DocImprint

Verify Evidence Bundle

verify_bundle

Read-onlyIdempotent

Verify the cryptographic integrity of an evidence bundle (ev_...) owned by your API key. Checks manifest hash, EIP-191 signature, and R2 artifact hashes. Free — no credits consumed. Use when you need to confirm a bundle has not been tampered with. For quick metadata lookups (without full crypto verification), use get_bundle instead. Returns: { valid: boolean, bundle_id, manifest_sha256, checks: { status, manifest_hash, signature, artifacts: [{ name, ok }] }, tampered: string[], signer_address: string|null, attestation_tx: string|null, url: string, captured_at: string } Example prompts:

"Verify the cryptographic integrity of bundle ev_550e8400."
"Is this evidence bundle still valid and untampered?"
"Deep-check the manifest hash and signature of my bundle."

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bundle_id`	Yes	Evidence bundle ID (ev_...) returned by extract or notarize. Example: "ev_550e8400-e29b-41d4-a716-446655440000"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No
`valid`	Yes
`checks`	Yes
`receipt`	Yes
`tampered`	Yes
`bundle_id`	Yes
`captured_at`	No
`attestation_tx`	No
`signer_address`	No
`manifest_sha256`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026
RemovedJul 26, 2026

Changed2 schema fields changedJul 17, 2026

addedOutput schema / properties / receipt

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "agent_id": {
+          "type": "string"
+        },
+        "algorithm": {
+          "const": "secp256k1-eip191",
+          "type": "string"
+        },
+        "bundle_id": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "manifest_sha256": {
+          "type": "string"
+        },
+        "receipt_id": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_at": {
+          "type": "string"
+        },
+        "signer_address": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "receipt_id",
+        "bundle_id",
+        "agent_id",
+        "action",
+        "manifest_sha256",
+        "signed_at",
+        "signature",
+        "signer_address",
+        "key_id",
+        "algorithm"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "bundle_id",
-  "valid",
-  "manifest_sha256",
-  "checks",
-  "tampered"
-]New value: +[
+  "bundle_id",
+  "valid",
+  "manifest_sha256",
+  "checks",
+  "tampered",
+  "receipt"
+]

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "attestation_tx": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "bundle_id": {
+      "type": "string"
+    },
+    "captured_at": {
+      "type": "string"
+    },
+    "checks": {
+      "additionalProperties": false,
+      "properties": {
+        "artifacts": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "actual": {
+                "type": "string"
+              },
+              "expected": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "ok": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "name",
+              "ok"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "attestation": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "manifest_hash": {
+          "type": "boolean"
+        },
+        "signature": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "status": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "status",
+        "manifest_hash",
+        "signature",
+        "artifacts",
+        "attestation"
+      ],
+      "type": "object"
+    },
+    "manifest_sha256": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "signer_address": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "tampered": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    },
+    "valid": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "bundle_id",
+    "valid",
+    "manifest_sha256",
+    "checks",
+    "tampered"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 24, 2026

changedInput schema / properties / bundle_id / description

Previous value: -"Evidence bundle ID (ev_...) returned by extract or notarize"New value: +"Evidence bundle ID (ev_...) returned by extract or notarize. Example: \"ev_550e8400-e29b-41d4-a716-446655440000\""

First observedJun 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint), but the description adds real value: what is actually checked (manifest hash, EIP-191 signature, R2 artifact hashes) and the cost model ('Free — no credits consumed'). It stops short of disclosing failure modes or latency, so a 4 rather than a 5.

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

Conciseness3/5

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

The core sentences are front-loaded and efficient, but the inline 'Returns:' block restates the output schema verbatim and the example prompts are boilerplate. Both duplicate structured data the agent already receives, diluting the concise core.

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

Completeness5/5

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

A single-parameter, read-only verification tool with an output schema, full annotation coverage, and a schema-documented parameter. Everything needed to select and invoke it correctly is present, including the sibling hand-off.

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% and the schema already documents bundle_id with the ev_ prefix and example. The description's '(ev_...)' and the ownership-by-API-key note marginally reinforce it but add no syntax or format detail beyond the schema. Baseline 3 is correct.

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 (verify), resource (evidence bundle), scope (cryptographic integrity), and ownership constraint (owned by your API key). It also explicitly routes away from get_bundle, so an agent can distinguish this from its closest sibling without opening the schema.

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

Usage Guidelines5/5

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

Gives the trigger condition ('confirm a bundle has not been tampered with') and names the alternative with the condition that selects it ('quick metadata lookups ... use get_bundle instead'). No inference required.

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

All DocImprint tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?