Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

McpTool

import type { McpTool } from "https://googleapis.deno.dev/v1/ces:v1.ts";
interface McpTool {
apiAuthentication?: ApiAuthentication;
description?: string;
inputSchema?: Schema;
name?: string;
outputSchema?: Schema;
serverAddress?: string;
serviceDirectoryConfig?: ServiceDirectoryConfig;
tlsConfig?: TlsConfig;
}

§Properties

§
apiAuthentication?: ApiAuthentication
[src]

Optional. Authentication information required to execute the tool against the MCP server. For bearer token authentication, the token applies only to tool execution, not to listing tools. This requires that tools can be listed without authentication.

§
description?: string
[src]

Optional. The description of the MCP tool.

§
inputSchema?: Schema
[src]

Optional. The schema of the input arguments of the MCP tool.

§
name?: string
[src]

Required. The name of the MCP tool.

§
outputSchema?: Schema
[src]

Optional. The schema of the output arguments of the MCP tool.

§
serverAddress?: string
[src]

Required. The server address of the MCP server, e.g., "https://example.com/mcp/". If the server is built with the MCP SDK, the url should be suffixed with "/mcp/". Only Streamable HTTP transport based servers are supported. This is the same as the server_address in the McpToolset. See https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http for more details.

§
serviceDirectoryConfig?: ServiceDirectoryConfig
[src]

Optional. Service Directory configuration for VPC-SC, used to resolve service names within a perimeter.

§
tlsConfig?: TlsConfig
[src]

Optional. The TLS configuration. Includes the custom server certificates that the client should trust.