Skip to main content
Glama

search_questions

Search this public knowledge base of short, accurate math and how-to answers. Use when the user asks a question that might already have a page here. Returns matching question ids, titles, short answers, and URLs. Read-only.

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_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum hits to return (default 8)
queryYesNatural-language question or keywords, e.g. 'how do I add fractions' or '2 + 3'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the safety burden and explicitly states "Read-only," while "public" clarifies the data scope. It also discloses the returned fields, though it gives no operational details such as ranking, freshness, or result-pagination behavior.

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?

Four short sentences efficiently cover purpose, usage, results, and safety in that order. The wording is front-loaded and contains no appreciable repetition or filler.

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 simple two-parameter search tool, it supplies domain scope, an invocation trigger, result contents, and read-only behavior. The fully documented schema covers the remaining invocation details, and describing the returned fields is especially useful because no output schema is provided.

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%, including query examples and the limit's default and bounds, so the baseline is 3. The description's reference to user questions reinforces the query use case but adds no substantial parameter meaning beyond the schema.

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?

The description pairs the specific verb "Search" with a clearly scoped resource: a public knowledge base of math and how-to answers. Listing matching question ids, titles, short answers, and URLs establishes this as a discovery tool rather than direct answer retrieval or feedback submission.

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?

It gives an explicit trigger: use it "when the user asks a question that might already have a page here." It does not provide exclusions or name get_answer as the follow-up for retrieving a selected result, so alternative-tool guidance remains incomplete.

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