Skip to main content
Glama

Search the Kaigen docs

search_docs
Read-onlyIdempotent

Search Kaigen's documentation and setup guide (CLI commands and their JSON answers, error codes, building, screenshots, publishing, plans). Returns the most relevant sections.

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
queryYesWhat to look up, in a few words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 needs no repetition. The description adds that it returns the most relevant sections, but says nothing about result count, ranking behavior, or what happens when nothing matches — useful gaps remaining.

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

Conciseness4/5

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

Two sentences, front-loaded with what is searched, and the parenthetical topic list is dense but earns its place by scoping the corpus. Minor cost: the list is long enough to slow scanning slightly.

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

Completeness4/5

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

For a one-parameter read-only search with full annotation coverage and no output schema, the definition supplies the important missing piece — what content is indexed. Only fallback behavior for empty results is absent, which is a small gap at this complexity.

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 coverage is 100% and the single query parameter is fully documented with length bounds and a 'few words' hint. The description's topic enumeration helps an agent phrase the query, but adds no syntax or format guidance beyond the schema.

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

Purpose4/5

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

The description names a specific verb (search) and resource (Kaigen documentation and setup guide) and enumerates the covered topics — CLI commands and their JSON answers, error codes, building, screenshots, publishing, plans. An agent knows exactly what corpus is searched, but nothing distinguishes it from siblings like about_kaigen or get_started.

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

Usage Guidelines3/5

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

Usage is only implied: it is a lookup tool for documentation content. There is no statement of when to prefer it over about_kaigen or get_started, and no exclusions for questions those siblings might answer better.

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.