Skip to main content
Glama

Verify a signed receipt / attestation

verify_receipt
Read-only

Confirm a persisted erasure receipt or knowledge attestation is authentic and unaltered by recomputing its canonical body and checking the Ed25519 signature with the public key.

Instructions

Verify a persisted erasure receipt or knowledge attestation: recompute its canonical body and check the Ed25519 signature. Confirms the artifact is authentic and unaltered — the same check a third party can run with only the public key.

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": {
      "receipt_id": "<receipt_id>"
    },
    "name": "verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receipt_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds real value on top by disclosing the internal behavior (canonical body recomputation, Ed25519 signature check) and the trust model (artifact is authentic and unaltered; verifiable by a third party holding only the public key). It does not say what happens on a failed verification or whether it raises versus returning a negative result, which is the remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and object, followed by the verification mechanism and trust framing. No filler, no repetition of the title or annotations.

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?

The tool is simple (one required param) and an output schema exists, so return values need not be explained. The description covers what is verified and how. It is close to complete; only failure semantics and ID provenance are left unaddressed.

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?

With one parameter at 0% schema description coverage, the description must carry the burden: it establishes that receipt_id refers to a persisted erasure receipt or knowledge attestation, which is genuine added meaning. However, it gives no format, scope, or provenance detail for that identifier (e.g., where the ID comes from), so it only partially compensates.

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 concrete verb (verify) plus the exact resource class (persisted erasure receipt or knowledge attestation) and the mechanism (recompute canonical body, check Ed25519 signature). An agent can tell what artifact this consumes. It stops short of explicitly contrasting with the sibling verify_audit, so sibling differentiation is only implied by artifact type.

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 — you call it on a persisted receipt/attestation to confirm authenticity — and the 'third party can run with only the public key' line hints at the verification scenario. There is no explicit when-to-use vs when-not-to-use guidance and no reference to the alternative check (verify_audit), leaving the routing decision to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.