Skip to main content
Glama

search

Search a RefLib corpus. Then read section IDs you need.

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": {
      "corpus": "<corpus>",
      "question": "<question>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
corpusYesCorpus id from list_corpora
questionYesPrecise question
n_resultsNoMaximum results (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses very little: no statement that this is a read-only/non-mutating operation, no mention of ranking or relevance behavior, no corpus-scoping or permission notes, and no hint about pagination or result volume beyond the n_results default. The only behavioral signal is that results include section IDs intended for follow-up reading.

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 short sentences with the core action front-loaded and no filler. The second sentence is awkwardly worded ("Then read section IDs you need") and could be tightened into a clearer workflow instruction, but nothing is padded.

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

Completeness3/5

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

With three fully documented parameters and no output schema, the main gap is return-value shape: the description only obliquely implies that results contain section IDs, without saying whether snippets, scores, or corpus metadata come back. It is minimally sufficient to call the tool but thin for interpreting results.

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%, so corpus, question, and n_results are already documented in the schema. The description adds no additional meaning about corpus scoping, question phrasing, or how n_results interacts with the two-step read workflow, so the baseline 3 applies.

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?

States a specific verb ("Search") and resource ("a RefLib corpus"), and the second sentence hints that results are section IDs consumable by the sibling "read" tool. It does not explicitly name "read" or "list_corpora" as alternatives, so sibling differentiation is only implied.

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?

The phrase "Then read section IDs you need" sketches a two-step workflow (search, then read), which implies when to use this tool. However, it never states when NOT to use it, nor does it explicitly point to "read" or "list_corpora" by name, leaving the routing 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.

Resources