Searches the official Vonage developer documentation for guides, tutorials, and API references. This is the primary tool for general queries about Vonage's products, services, and APIs, and should be used when the user asks for information, documentation, or how-to guides.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The user's search query, which can be a keyword, phrase, or a question about Vonage's APIs or documentation |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Searches' which implies a read-only operation, but it does not mention output format, limitations, or any side effects. The description adds minimal behavioral context beyond the tool's name.
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?
The description is two concise sentences with no redundant wording. It front-loads the core purpose and then provides usage context, making it easy to parse quickly.
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?
Given the simplicity of the tool (one parameter, no output schema), the description covers the main function and usage context. However, it does not describe what the search returns or any behavioral expectations, which would be helpful for the agent to set user expectations or handle results.
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?
The schema provides 100% coverage for the single 'query' parameter with a clear description. The tool description adds no additional parameter semantics, so it correctly falls at the baseline of 3 for fully documented schemas.
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?
The description clearly states the tool's function: searching official Vonage developer documentation for guides, tutorials, and API references. It identifies itself as the primary tool for general queries, which subtly distinguishes it from more specific sibling tools, though it does not name alternatives explicitly.
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?
The description provides explicit guidance on when to use the tool: 'should be used when the user asks for information, documentation, or how-to guides.' However, it does not discuss when not to use it or direct to specific sibling tools for niche needs, leaving some ambiguity for the agent.
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.
