| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Plain-language description of the capability you need, e.g. 'query a Postgres database'. | |
| maxResults | No | How many ranked matches to return (default 5). | |
| requireRemote | No | Only return servers with a hosted remote endpoint (usable immediately). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The two tools have clearly distinct purposes: one for proxying tool calls with security guards, the other for discovering servers. No overlap.
Both tool names follow a verb_noun pattern in snake_case, maintaining consistency.
With only 2 tools, the surface is minimal, but they cover the core proxy and discovery functions. Could benefit from additional tools like listing available servers or managing connections.
The tool set lacks basic discovery functionality (e.g., listing servers) and management tools, making it incomplete for a gateway's full lifecycle.
