Skip to main content
Glama

undocsend docs

Search undocsend docs

search_docs
Read-onlyIdempotent

Search the undocsend documentation, plus the features, pricing and security pages. Returns ranked pages with title, path, HTML URL, markdown URL and a snippet. Follow up with get_doc to read a page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return (1-20, default 5).
queryYesWhat to look for, in plain words, e.g. "require an NDA before viewing" or "watermark".

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are ranked and names the snippet/title/URL fields plus the get_doc handoff, which is genuine extra context. It adds nothing about ranking behavior, result limits beyond the schema, or what happens when nothing matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: what is searched, what comes back, what to do next. Purpose is front-loaded and no sentence is filler, though the return-value sentence partly duplicates the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety, an output schema covering the result shape, and full schema description coverage, the description needs only to frame purpose and next step — which it does. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented in-schema with examples and bounds (limit 1-20 default 5, query max 200 chars). The description adds no meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search the undocsend documentation") and scopes the corpus to docs plus the features, pricing and security pages. An agent can tell this apart from get_doc because the description explicitly frames get_doc as the read-a-page follow-up.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit workflow: search first, then "Follow up with get_doc to read a page." That is clear context for the primary use case. It does not say when to prefer this over list_docs or when browsing beats searching, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.