Skip to main content
Glama

Stream Presence — Receipt Verifier

Verify a receipt

verify_receipt
Read-onlyIdempotent

Full recompute of one receipt from the public log: log chain intact, issuer Ed25519 signature, issuer registration/class, per-issuer chain link, approval binding, outcome, disputes and countersignatures. Returns the per-check verdict object — never a bare boolean. Give receipt_id, or a full receipt object (its signature is checked and it is compared byte-for-byte with the log entry).

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": "verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptNoA full receipt object to verify
receipt_idNoReceipt id, rcpt_…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered structurally. The description adds genuine value beyond that: it discloses the return shape ('per-check verdict object — never a bare boolean') and that an input receipt's signature is verified and compared byte-for-byte, which is non-obvious behavior with no output schema to document it. It does not, however, describe cost, latency, or what happens when a check fails or the receipt is absent from the log.

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?

Two sentences, front-loaded with the core action and the enumerated checks, followed by input guidance. No filler, though the check list is dense and the second sentence carries the crucial return-shape caveat in a trailing clause rather than a lead position.

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?

For a two-input verification tool with no output schema, the definition covers the important ground: what is checked, what comes back, and how to supply input in either mode. The gap is the absence of any statement about being required to supply one of the two optional parameters, and about failure/absent-receipt behavior, which matters for a verifier whose whole job is reporting problems.

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%, so both parameters are already documented in the schema, which sets the baseline at 3. The description does add meaning beyond the schema for the receipt object (its signature is validated and it is diffed against the log entry) and clarifies the either/or relationship between the two inputs, but adds nothing for receipt_id beyond the 'rcpt_…' format already given.

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 and resource ('Full recompute of one receipt from the public log') and enumerates exactly what is re-checked: log chain, issuer Ed25519 signature, issuer registration/class, chain link, approval binding, outcome, disputes, countersignatures. This is clearly distinguishable from a passive fetch like get_receipt, since verification implies independent recomputation rather than retrieval.

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 second sentence gives concrete invocation guidance for both modes: pass receipt_id, or pass a full receipt object whose signature is checked and byte-compared against the log entry. The condition selecting the second mode (you already hold the signed object) is implied well. It stops short of stating when to prefer this over get_receipt or issuer_standing, so no explicit alternatives or exclusions.

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