Skip to main content
Glama

SW Accounting documentation

Search documentation

search_docs
Read-onlyIdempotent

Search the pages and articles of sw-cpas.com, including the developer, API and agent documentation. Use it to find which page answers a question; returns titles, URLs and markdown URLs, best match first. Read a result with fetch_doc.

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
limitNoMaximum number of results (1-20).
queryYesWords or a question to search for.

Output Schema

NameRequiredDescriptionDefault
queryNoThe query that was searched.
resultsYesMatches with url, name, score, description and markdown_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: it discloses the return fields (titles, URLs, markdown URLs) and the ranking behavior ("best match first"), which shapes how an agent should interpret result order. It stops short of stating result-count defaults or behavior on zero 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, front-loaded with the scope and purpose, then the usage condition, then the follow-up action. Every sentence carries information an agent needs; there is no filler or repetition of the name.

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?

For a two-parameter read-only search with full schema coverage and an output schema, this covers purpose, when to use, result ordering, and the natural next step. Nothing an agent needs in order to call it correctly is absent.

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 self-documenting, so the baseline is 3. The description's "find which page answers a question" hints that natural-language queries are acceptable, but the schema field already says "Words or a question to search for," so no real meaning is added.

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 ("Search") and a precise resource ("the pages and articles of sw-cpas.com, including the developer, API and agent documentation"), and its scope as a discovery tool is clearly distinct from the fetch_doc sibling that retrieves content.

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

Usage Guidelines5/5

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

"Use it to find which page answers a question" gives an explicit when-to-use condition, and "Read a result with fetch_doc" names the alternative with the exact condition that selects it. Nothing about routing between the two tools is left to inference.

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.