Skip to main content
Glama

get_statement

Read-only

Everything the register holds about one statement: formalisations, cited proofs, recompilation results, graded claims, relations and aliases.

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": {
      "id": "<id>"
    },
    "name": "get_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCanonical id or any alias, e.g. erdos:707

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already establishes a safe read, and the description usefully adds payload composition beyond that annotation, signaling a broad aggregate response. However, it says nothing about response size, cost, or whether unfound ids error versus return empty, which matters for a tool that bundles many sub-resources.

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?

A single front-loaded sentence with no filler; the enumeration earns its place by disclosing returned content. It is a verbless fragment, though, which is slightly less scannable than 'Retrieve everything...' would be.

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?

With one required parameter, full schema coverage, and no output schema, the description's enumeration of returned data carries the return-value burden well. Missing only edge-case behavior such as unknown ids and payload size, which are minor for a simple read lookup.

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 coverage is 100% and the schema itself explains that id accepts a canonical id or any alias (e.g. erdos:707). The description adds no further constraint or format detail, so the baseline 3 applies while the schema does the work.

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 resource ('one statement') and enumerates exactly what is returned (formalisations, cited proofs, recompilation results, graded claims, relations, aliases), which tells an agent this is an aggregate fetch rather than a narrow sub-entity lookup. It stops short of naming a sibling such as get_formalisation or search_statements to contrast with, so the boundary is implied rather than stated.

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?

Usage is only implied: an agent can infer this is the tool for pulling a complete record given a known id, but there is no explicit when-to-use, when-not-to-use, or directive to use search_statements first to find an id. No alternatives are named despite a crowded sibling set of narrow get_* lookups.

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