Skip to main content
Glama

stamp_description

Read-only

Validate a client-produced scene reading and stamp provenance.

This is the interpretation boundary for the no-key kit path: you read the
picture ``describe_scene`` returned, produce
``{summary, observed_features, confidence, caveats}``, and pass it here.
The library checks the shape, stamps CC-BY and the AI-interpretation
note (the model never sets those), and — when ``image`` is the record
from the kit — appends a deterministic caveat if the picture was a
smaller baked preview. Until this returns, the reading is unvalidated
prose, not pipeline output.

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

Input Schema

NameRequiredDescriptionDefault
assetNoProduct the reading describes. Default GEC.GEC
imageNoImage record from the describe_scene kit. A smaller baked preview appends a caveat.
modelNoModel name to record. Default client-kit when omitted.
item_idNoAcquisition id to record on the stamped reading. Omit to leave it unset.
readingYesClient JSON with summary, observed_features, confidence, and caveats.

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 reading describes. Default GEC."
    • addedInput schema / properties / image / description
      Added value: +"Image record from the describe_scene kit. A smaller baked preview appends a caveat."
    • addedInput schema / properties / item_id / description
      Added value: +"Acquisition id to record on the stamped reading. Omit to leave it unset."
    • 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, observed_features, confidence, and caveats."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real behavioral context: the library performs shape checks, stamps CC-BY plus an AI-interpretation note that the model cannot set, and conditionally appends a deterministic caveat when `image` is a smaller baked preview. That is well beyond the annotation. It does not fully clarify that stamping is non-destructive (a returned copy rather than a mutation of stored state), though 'Until this returns' implies a pure function, so no contradiction with readOnlyHint.

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?

Front-loaded with the one-line purpose, then a single structured paragraph covering position in the pipeline, input shape, and side effects. Every sentence carries information, though the middle paragraph is somewhat dense and the parenthetical about the model never setting stamp fields could be tightened.

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?

For a validation/stamping tool with five parameters, a nested reading object, full schema coverage, and an output schema, the description covers what an agent needs: when to call it, what shape to supply, and what the library does that the caller cannot control. Return-value details are rightly omitted given the output schema exists.

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 adds meaning the schema does not: it enumerates the expected `reading` payload (`{summary, observed_features, confidence, caveats}`) and explains the `image` parameter's conditional effect (a smaller baked preview appends a caveat). Other params (asset, item_id, model) are left to the schema, which already documents them well.

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?

States a specific verb pair and resource: validate a client-produced scene reading and stamp provenance. It also positions the tool relative to its sibling by describing the division of labor with `describe_scene` ('you read the picture describe_scene returned, produce {...}, and pass it here'), so an agent can distinguish the producer from the validator 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use context: this is the step that turns a raw reading into pipeline output, and until it returns the reading is 'unvalidated prose.' It also states the input precondition (the reading comes from the describe_scene picture). It stops short of naming the alternative path (e.g. stamp_narration) or stating when this tool should be skipped, which keeps it from a 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.