DocImprint

Get Evidence Bundle

get_bundle

Read-onlyIdempotent

Retrieve metadata for an evidence bundle (ev_...) owned by your API key. Free — no credits consumed. Use for quick status/metadata lookups such as checking if a bundle is complete, finding its notarization status, or viewing retention/legal hold info. For deep cryptographic integrity verification (hash + signature + artifact checks), use verify_bundle instead. Returns: { bundle_id, source_url, mode, status: "pending"|"complete"|"failed", manifest_sha256, manifest_signature, signer_address, attestation_tx, attestation_at, eas_uid, parent_bundle_id, superseded_by, legal_hold: boolean, retention_until, created_at } Example prompts:

"Show me the metadata for bundle ev_550e8400."
"Check the status and notarization info of my evidence bundle."
"Get me the details of bundle [ev_id] — is it complete?"

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes
`status`	Yes
`eas_uid`	Yes
`receipt`	Yes
`bundle_id`	Yes
`created_at`	Yes
`legal_hold`	Yes
`source_url`	Yes
`superseded_by`	Yes
`attestation_at`	Yes
`attestation_tx`	Yes
`signer_address`	Yes
`manifest_sha256`	Yes
`retention_until`	Yes
`parent_bundle_id`	Yes
`manifest_signature`	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",
-  "source_url",
-  "mode",
-  "status",
-  "manifest_sha256",
-  "manifest_signature",
-  "signer_address",
-  "attestation_tx",
-  "attestation_at",
-  "eas_uid",
-  "parent_bundle_id",
-  "superseded_by",
-  "legal_hold",
-  "retention_until",
-  "created_at"
-]New value: +[
+  "bundle_id",
+  "source_url",
+  "mode",
+  "status",
+  "manifest_sha256",
+  "manifest_signature",
+  "signer_address",
+  "attestation_tx",
+  "attestation_at",
+  "eas_uid",
+  "parent_bundle_id",
+  "superseded_by",
+  "legal_hold",
+  "retention_until",
+  "created_at",
+  "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_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "attestation_tx": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "bundle_id": {
+      "type": "string"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "eas_uid": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "legal_hold": {
+      "type": "boolean"
+    },
+    "manifest_sha256": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "manifest_signature": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "mode": {
+      "type": "string"
+    },
+    "parent_bundle_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "retention_until": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "signer_address": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "source_url": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "pending",
+        "complete",
+        "failed"
+      ],
+      "type": "string"
+    },
+    "superseded_by": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "bundle_id",
+    "source_url",
+    "mode",
+    "status",
+    "manifest_sha256",
+    "manifest_signature",
+    "signer_address",
+    "attestation_tx",
+    "attestation_at",
+    "eas_uid",
+    "parent_bundle_id",
+    "superseded_by",
+    "legal_hold",
+    "retention_until",
+    "created_at"
+  ],
+  "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_bundle"New value: +"Evidence bundle ID (ev_...) returned by extract or notarize_bundle. 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 establish readOnlyHint and idempotentHint. The description adds genuine context beyond them: 'Free — no credits consumed,' the meaning of status values (pending/complete/failed), and fields like superseded_by and legal_hold that signal bundle lifecycle. It does not cover error behavior for a nonexistent or foreign-owner bundle, so it stops short of 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.

Conciseness4/5

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

The purpose, cost, and sibling routing are front-loaded in the first two sentences. The verbatim Returns block is somewhat redundant since an output schema exists, and the three example prompts pad the definition, but nothing is misleading.

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 single-parameter read tool with an output schema and safety annotations, the description covers purpose, cost, routing, and use cases completely. Minor redundancy in restating the return shape rather than a gap, though ownership/auth failure behavior is 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?

Only one parameter and schema coverage is 100%, so the schema already documents the ev_... format and its origin. The description adds only the ownership scoping note ('owned by your API key'), which is useful but not a syntactic or semantic expansion. Baseline 3 applies.

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 (retrieve) and resource (metadata for an evidence bundle), scopes it to the caller's API key, and explicitly distinguishes itself from verify_bundle, which handles deep cryptographic verification. An agent can route between the two without opening either 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 concrete when-to-use cases (checking completeness, notarization status, retention/legal hold) and names the alternative tool plus the condition that selects it ('for deep cryptographic integrity verification... use verify_bundle instead').

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?