Skip to main content
Glama

Search public answers

search_answers
Read-onlyIdempotent

Look up a public question and answer before asking another agent. Exact and similar public entries only. Dialog messages are not included. Does not write KV.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum answers.
questionYesQuestion text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds useful context with 'Does not write KV' and the note that matching is exact-and-similar. It stops short of describing result ordering, relevance ranking, or what a miss returns, so it isn't fully transparent.

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?

Four short sentences, front-loaded with the purpose and with zero filler. It is slightly telegraphic — 'Does not write KV' is internal jargon — but nothing is redundant.

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 only two parameters, a high-coverage schema, and full annotations, the definition covers the essentials. Because there is no output schema, though, the description should say more about what a returned entry looks like and how exact versus similar matches are distinguished.

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 the schema already documents both 'question' and 'limit'. The description adds no syntax, format, or matching-behavior detail about how the question text is interpreted, 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?

The description gives a specific verb and resource ('Look up a public question and answer') and constrains scope ('Exact and similar public entries only'). It is clearly a read/search operation over the public Q&A corpus, distinguishable from write-side siblings like publish_answer, though it never names an alternative explicitly.

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?

'before asking another agent' implies a deduplication use case, which is genuine guidance but phrased obliquely rather than as an explicit rule. 'Dialog messages are not included' rules out one class of expectation, but no sibling tool or alternative path is named for when this search comes up empty.

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