search_docsFull-text search across Vector Panda concepts, tutorials, projects, and the engineering build log. Returns ranked matches with canonical URLs and freshness.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results (default 5, cap 20) | |
| query | Yes | Search terms |
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?
The annotations already indicate readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, making the safe, non-mutating nature explicit. The description adds behavioral details about the return format (ranked matches with canonical URLs and freshness), which goes beyond the annotations. However, it does not mention pagination or other response details, but that is not a significant omission given the annotations.
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 compact and information-dense, consisting of two sentences that convey the purpose, scope, and output without any redundancy. It is well-structured and front-loads the essential action and resource. No unnecessary details or filler are present.
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 that there is no output schema, the description adequately specifies what the tool returns (ranked matches with canonical URLs and freshness). The parameter descriptions in the schema cover the inputs. The context of being a search tool is complete enough for an agent to decide when to use it, though it could benefit from a brief note on how results are ordered or whether any filters are applied, but this is not critical.
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 descriptions for both parameters ('Search terms' and 'Maximum results (default 5, cap 20)') are clear and fully cover their meaning, giving 100% schema_description_coverage. The tool description does not add any additional semantic nuance about the parameters beyond what is already in the schema. Therefore, the baseline score of 3 is appropriate.
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 it is a full-text search across specific content types (concepts, tutorials, projects, engineering build log) and specifies what it returns (ranked matches with URLs and freshness). This distinguishes it from sibling tools like read_doc, which likely fetch a specific document, and list_supported_formats. The verb 'search' is explicit and the resource scope is defined.
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 clear context on when to use this tool—when needing to search across the documentation corpus. It does not explicitly mention alternatives or exclusions, but the sibling tool list and the nature of a search tool make it apparent that this is the appropriate choice for discovery rather than direct retrieval. The absence of explicit 'when not to use' statements is a minor gap, but the context is sufficiently clear.
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.
Most tools have clearly distinct purposes: search, read, API reference, quickstart, formats, benchmarks. The main overlap is between compare_storage_tiers and get_pricing, which both cover storage-tier pricing and could confuse an agent.
The set mostly follows a predictable get_/list_/read_/search_ verb pattern with snake_case throughout. Minor deviation: read_doc and search_docs use navigation verbs instead of get_/list_, but the pattern remains readable.
Eight tools is well-scoped for a documentation-focused server. Each tool covers a meaningful documentation need without redundancy or bloat.
The surface covers the full documentation workflow: searching docs, reading docs, quickstart, API operations, pricing, storage tiers, formats, and benchmarks. No obvious dead ends or missing core operations.