gateway_invoke
Invoke tools across backend servers through a unified gateway with authentication, rate limiting, caching, and failsafe middleware. Discover available tools first using gateway_search_tools.
Instructions
Invoke any tool on any backend server. Routes through the gateway's auth, rate-limit, caching, and failsafe middleware. Use gateway_search_tools first to discover the right tool and server.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| arguments | No | Tool arguments | |
| server | Yes | Backend server name | |
| tool | Yes | Tool name to invoke |
Implementation Reference
- benchmarks/token_savings.py:120-144 (schema)The tool definition (schema) for "gateway_invoke". Note that the actual handler implementation logic resides in the binary `mcp-gateway` (as per the context in `npm/run.js`), while this file defines its expected schema for benchmarking purposes.
"name": "gateway_invoke", "description": ( "Invoke a specific tool on a specific backend server. " "Pass the server name, tool name, and arguments. " "The gateway routes the request and returns the result." ), "inputSchema": { "type": "object", "properties": { "server": { "type": "string", "description": "Name of the backend MCP server.", }, "tool": { "type": "string", "description": "Name of the tool to invoke.", }, "arguments": { "type": "object", "description": "Arguments to pass to the tool.", }, }, "required": ["server", "tool"], }, },