Skip to main content
Glama

search_statements

Read-only

Search the register of mathematical statements. Returns summaries with formal status, prizes, and how much AI work is recorded against each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_statements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoText to match in id, title, collection or tags
has_prizeNo
collectionNoRestrict to one collection
has_ai_claimNo
formal_statusNo
verified_onlyNoOnly statements with a proof recompiled here

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful information about the summary results and their contents, but does not explain result ordering, pagination, or what the amount of recorded AI work concretely represents.

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?

The two sentences are compact and front-load the operation and resource. The second sentence earns its place by describing the returned summaries without unnecessary wording.

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?

The description and schema are sufficient for a basic search invocation, and the description partially compensates for the absence of an output schema by naming key summary fields. For a seven-parameter search tool, however, it omits useful filter behavior, result navigation, and guidance on when to use a detail-oriented sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage of 43%, the description needs to compensate for undocumented parameters, but it discusses only the resource and returned fields. It adds no guidance on combining filters, interpreting has_prize or has_ai_claim, using the limit, or how formal_status and verified_only affect searches.

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: searching the register of mathematical statements. It also clarifies that results are summaries covering formal status, prizes, and recorded AI work, but it does not explicitly distinguish this tool from siblings such as get_statement or the other search tools.

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 wording implies that the tool is for discovering statements rather than retrieving one known statement, which provides some usage context. It gives no explicit when-to-use guidance, prerequisites, or alternatives for detailed records or adjacent searches.

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