Skip to main content
Glama

verify_evidence_bundle

Re-checks an evidence bundle's Git state and file hashes against the live workspace to return verified, stale, failed, or unverifiable status.

Instructions

Re-checks Git state and file hashes against live workspace. Returns verified, stale, failed, or unverifiable status.

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

Input Schema

NameRequiredDescriptionDefault
bundleIdYesThe unique identifier of the evidence bundle to verify.
workspacePathNoOptional workspace path hint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the whole burden, and it partially does so by enumerating the four outcome statuses (verified, stale, failed, unverifiable), which is genuinely useful decision-relevant behavior. It still does not say whether verification mutates the bundle or workspace, what permissions are needed, or what distinguishes 'stale' from 'unverifiable', so key behavioral questions remain open.

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 with zero filler; the action is front-loaded and the outcome vocabulary follows immediately. Nothing would be gained by restructuring.

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 two-parameter verification tool with no output schema, disclosing the possible return statuses covers most of what an agent needs. The remaining gap is that the semantics of those statuses — especially stale versus unverifiable — are not explained, which matters because there is no output schema to fall back on.

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, and the baseline of 3 applies. The description adds only indirect context — 'live workspace' hints at what workspacePath influences — but gives no detail on how the path hint affects resolution or whether bundleId is sufficient on its own.

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 gives a specific verb ('Re-checks') and concrete resources ('Git state and file hashes against live workspace'), so an agent knows exactly what operation is performed. It does not explicitly distinguish itself from nearby siblings such as verify_replay_proof or check_bundle_quorum, which keeps it short of a 5.

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 only implied: 'Re-checks' and 'against live workspace' suggest it is for re-validating an already-created bundle whose underlying files or commits may have drifted. There is no explicit statement of when to prefer this over verify_replay_proof nor any precondition or exclusion.

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