MCP Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gateway_statusB | 查看网关已配置子服务的健康状态、前缀和工具数量 |
| search_gateway_toolsA | 搜索 gateway 下真实可调用的工具。返回紧凑结果：工具名、单行描述、必填参数、少量可选参数预览。 |
| describe_gateway_toolA | 按工具名查看单个 gateway 工具的详细 schema。先用 search_gateway_tools 搜，再按需 describe。 |
| call_gateway_toolA | 调用 gateway 下某个真实工具。name 来自 search_gateway_tools / describe_gateway_tool，arguments 为该工具的真实参数字典。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: status check, search, detailed schema lookup, and invocation. There is no overlap between them, and an agent can easily select the right tool for the task.
Three tools follow the verb_noun pattern (search_gateway_tools, describe_gateway_tool, call_gateway_tool), while gateway_status uses noun_verb order. This is a minor deviation but the overall pattern remains predictable and readable.
Four tools is well-scoped for a gateway meta-server that provides discovery, inspection, and invocation. Each tool earns its place, and the count is not excessive or thin.
The set covers the core lifecycle of interacting with underlying tools: status, search, describe, and call. A minor gap is the lack of a direct 'list all tools' operation, but search_gateway_tools effectively serves that purpose.