Skip to main content
Glama

Search the Casama docs

search_docs
Read-only

Search Casama's documentation by keyword to find the best-matching sections with their page address. Use it to locate guides, API, CLI, SDK, plugin, webhook, and self-hosting topics.

Instructions

Keyword search over docs.casama.ai (guides, self-hosting, the API, CLI, SDKs, plugins, webhooks, A2A, bot templates, contributing). Returns the best-matching sections with their address; read a whole page with read_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
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavior beyond that: the search is keyword-based (implying no semantic matching) and returns best-matching sections with their address rather than full pages. It omits result-count/pagination behavior and the meaning of the limit cap, which keeps it below a 5.

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?

Two sentences, front-loaded with the core action and scope, then the return shape and the follow-up sibling. The parenthetical domain list is dense but earns its space by defining coverage; nothing is redundant.

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 two-parameter read-only search with no output schema, the description covers what is returned (matching sections plus their address) and the natural next step (read_doc). A small gap remains around result volume and what a "section address" looks like, but the essentials for correct invocation are present.

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 0%, so the description must carry parameter meaning. It clarifies that the query is a keyword search, which is genuinely useful, but says nothing about limit (its range 1-10, default, or effect on result quality) or about the 2-500 character query bound, leaving half the parameters undocumented in both places.

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+resource ("keyword search over docs.casama.ai") and enumerates the content domains covered (guides, self-hosting, API, CLI, SDKs, plugins, webhooks, A2A, bot templates, contributing). It also names the sibling read_doc for full-page reads, so an agent can distinguish the two without opening either schema.

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?

Clear usage context: use this to find matching sections, then follow up with read_doc for a whole page. It does not cover when to prefer list_doc_pages or get_api_operation, nor does it state any exclusions, so the routing guidance is good but not exhaustive.

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