Skip to main content
Glama

The history of one statement

get_statement
Read-onlyIdempotent

Use this when you cite a value and need to know whether it changed, was corrected or withdrawn, or to re-check a value you stored earlier. Every attribute from get_product carries a statement_id that stays the same across new values, withdrawals and merges; this returns every version oldest first (value, verification_state, confidence_recorded, recorded_at, ended_by superseded/withdrawn with the reason, sources) and the changes attached to it, each marked if it was corrected.

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

Input Schema

NameRequiredDescriptionDefault
statement_idYesThe statement_id from an attribute or scoped value of get_product, or from a change.

Output Schema

NameRequiredDescriptionDefault
changesYes
contractYes
page_urlYes
versionsYes
attributeNo
statement_idYes
version_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by explaining that versions are returned oldest first, that statement_id remains stable across new values, withdrawals and merges, and what fields each version carries. It omits pagination or volume behavior, so a 4 rather than 5.

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?

The definition is two sentences with the usage trigger front-loaded and the return shape consolidated. It is dense but every clause carries relevant information. Some field enumeration overlaps with the existing output schema, making it slightly longer than strictly needed.

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?

Since an output schema exists, return values needn't be spelled out, yet the description still characterizes version ordering and the attached-change structure, which is helpful. For a single-parameter read tool with rich annotations, the definition covers what an agent needs. Minor omission of pagination or volume expectations keeps it at 4.

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

Parameters4/5

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

With one parameter at 100% schema coverage, the baseline is 3. The description adds meaning beyond the schema by explaining that the statement_id stays the same across new values, withdrawals and merges, which clarifies why one ID can yield a full history. The schema already documents the ID's origin, so this is an incremental rather than large addition.

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 states a specific action and resource: it returns every version of a statement, oldest first, along with attached changes. It also ties the statement_id back to get_product attributes, which helps an agent place the tool. It does not explicitly distinguish itself from similar history-style siblings like get_product_changes, so it falls just short of a 5.

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?

The opening sentence gives concrete when-to-use guidance: citing a value and needing to know if it changed, was corrected, or withdrawn, or re-checking a stored value. It does not name a specific alternative tool or state when not to use this one, which keeps it below 5.

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