Skip to main content
Glama

stamp_narration

Read-only

Validate a client-produced change narration and stamp provenance.

Sibling of :func:`stamp_description` for the no-key ``narrate_change``
kit. Pass the JSON you produced plus the ``change_stats`` grid from the
kit so the stamped object carries the numbers the prose was grounded in.

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": {
      "reading": "<reading>"
    },
    "name": "stamp_narration"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoProduct the narration describes. Default GEC.GEC
modelNoModel name to record. Default client-kit when omitted.
readingYesClient JSON with summary, changes, confidence, and caveats.
item_idsNoAcquisition ids the narration covers.
change_statsNoPer-block decibel grid from the narrate_change kit, stored on the stamped object.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / asset / description
      Added value: +"Product the narration describes. Default GEC."
    • addedInput schema / properties / change_stats / description
      Added value: +"Per-block decibel grid from the narrate_change kit, stored on the stamped object."
    • addedInput schema / properties / item_ids / description
      Added value: +"Acquisition ids the narration covers."
    • addedInput schema / properties / model / description
      Added value: +"Model name to record. Default client-kit when omitted."
    • addedInput schema / properties / reading / description
      Added value: +"Client JSON with summary, changes, confidence, and caveats."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so behavioral disclosure is largely left to the description. It usefully explains that the stamped object carries the grounding numbers, but leaves open whether the stamp persists anywhere and what a failed validation returns — precisely the ambiguity an agent needs resolved given readOnlyHint on a tool named 'stamp'.

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 sentences, front-loaded with the action, with no wasted preamble. Minor noise comes from reStructuredText roles and double-backtick markup (':func:', '``narrate_change``'), which are formatting artifacts rather than information an agent needs.

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?

An output schema exists, so return values need no explanation, and the input-to-output linkage is well described. What remains missing for a five-parameter validation tool is what the validation actually checks and how rejection is signaled, which is the core unknown an agent faces before calling it.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns above baseline by explaining the relationship between inputs: the 'reading' object is what the agent produced, and 'change_stats' is the per-block grid from the kit that grounds the prose numbers. That adds purpose-level meaning the field descriptions alone do not convey.

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 verb pair and resource: 'Validate a client-produced change narration and stamp provenance.' It also distinguishes itself from the similarly named sibling by naming it and tying this tool to the 'no-key narrate_change kit', which lets an agent infer the keyed-vs-no-key split without opening either schema.

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 implied through the workflow ('pass the JSON you produced plus the change_stats grid from the kit'), which tells an agent where the inputs come from. However, it never states explicitly when to pick this over stamp_description, narrate_change, or change_composite, nor what an agent should use if it has no client-produced narration.

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.