Skip to main content
Glama

export_verification_proof

Verifies an evidence bundle and issues a cryptographically signed, portable Ed25519 proof saved to .evidence-mcp/proofs/ for tamper-evident sharing.

Instructions

Verifies an evidence bundle and issues a cryptographically signed, portable Ed25519 verification proof saved to .evidence-mcp/proofs/.

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": {
      "bundleId": "<bundleId>"
    },
    "name": "export_verification_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleIdYesThe unique identifier of the evidence bundle to verify and certify.
privateKeyPemNoOptional PEM-encoded private key for signing (defaults to local agent key).
workspacePathNoOptional workspace path hint to locate the bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits — that this is a write operation producing a file at .evidence-mcp/proofs/, and that signing is Ed25519-based — but it omits what happens on verification failure, whether existing proofs are overwritten, and what permissions or key material are required.

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 dense sentence that front-loads the core action and ends with the concrete output location. Nothing is wasted, though the packing of verify + sign + persist into one clause makes it slightly dense.

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 tool with no annotations and no output schema, the description covers what is produced (a signed proof file) but not the return shape an agent should expect, nor failure semantics when verification does not pass. Adequate but with clear gaps for a signing/mutation tool.

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 description coverage is 100%, so bundleId, privateKeyPem, and workspacePath are already documented in the schema. The description adds only the notion that the bundle is being 'verified and certified' and says nothing about the optional private key override or workspace hint, so it neither compensates nor detracts.

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 pair (verifies, issues) and a concrete artifact (a cryptographically signed, portable Ed25519 verification proof) plus its destination path. It is clearly distinguishable from capture_* or create_evidence_bundle siblings, though it does not explicitly contrast itself with the closely named verify_evidence_bundle or verify_replay_proof.

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 explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites (e.g. whether the bundle must already exist or be signed). The presence of siblings like verify_evidence_bundle and export_evidence_report makes the absence of routing guidance a real gap for an agent choosing between them.

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