Skip to main content
Glama

verify_replay_proof

Verifies the cryptographic signature and bundle consistency of an exported verification proof, optionally checking it against live workspace state.

Instructions

Verifies the cryptographic signature and bundle consistency of an exported verification proof.

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

Input Schema

NameRequiredDescriptionDefault
proofIdNoThe ID of the proof stored in .evidence-mcp/proofs/ (e.g. "proof_12345678").
bundleIdNoOptional bundle ID to verify consistency with live workspace state.
proofJsonNoRaw JSON string of a verification proof.
workspacePathNoOptional workspace path hint to locate bundle and proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says what is checked but not what happens on failure, whether any evidence is mutated or written, whether special permissions or trusted agents are required, or what a successful verification returns.

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?

A single tight sentence with the core object front-loaded and no filler. It is efficient, though its brevity is also the source of the missing guidance noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four parameters, zero required fields, no annotations, and no output schema, the description does far too little. It never explains how the optional inputs combine (e.g., whether proofId or proofJson should be supplied, or how bundleId and workspacePath are used), which is exactly the ambiguity an agent needs resolved before calling.

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

Parameters2/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 nothing about parameter semantics. Critically, all four parameters are optional and include two mutually alternative input modes (proofId vs proofJson), which the description never explains or reconciles with bundleId and workspacePath.

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 names a specific verb ('Verifies') and specific objects ('cryptographic signature and bundle consistency of an exported verification proof'), which is far more informative than a restatement of the name. It does not, however, distinguish this from the sibling verify_evidence_bundle, leaving the agent to guess which of the two verification tools applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as verify_evidence_bundle or export_verification_proof. The agent must infer from the name alone that this is for pre-exported proof artifacts rather than live bundles.

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