DocImprint

Notarize Bundle On-Chain

notarize_bundle

Idempotent

Notarize an evidence bundle on-chain by writing its manifest SHA-256 to the blockchain (Base/EVM). Creates a permanent, tamper-evident on-chain record of the document fingerprint. If the bundle is already notarized, returns the existing attestation immediately (idempotent). Use when you need an immutable on-chain timestamp proving a document existed at a point in time. For quick integrity checks without on-chain cost, use verify_bundle instead. PREREQUISITE: Bundle status must be "complete". Check status with get_bundle first. NOTE: Costs gas (ETH). The on-chain record is permanent and cannot be deleted even if the bundle is later purged. Returns: { bundle_id, attestation: { tx_hash, network, attested_at, key_id, eas_uid?, schema_uid? } } Example prompts:

"Notarize bundle ev_550e8400 on-chain so I have a permanent record."
"Put the fingerprint of my evidence bundle on the blockchain."
"Create an on-chain timestamp for this document bundle."

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bundle_id`	Yes	Evidence bundle ID (ev_...) to notarize. Bundle must have status "complete". Example: "ev_550e8400-e29b-41d4-a716-446655440000"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`receipt`	Yes
`bundle_id`	Yes
`attestation`	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",
-  "attestation"
-]New value: +[
+  "bundle_id",
+  "attestation",
+  "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": {
+      "additionalProperties": false,
+      "properties": {
+        "attested_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "eas_uid": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "network": {
+          "type": "string"
+        },
+        "schema_uid": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "tx_hash": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "tx_hash",
+        "network",
+        "attested_at"
+      ],
+      "type": "object"
+    },
+    "bundle_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "bundle_id",
+    "attestation"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 24, 2026

changedInput schema / properties / bundle_id / description

Previous value: -"Evidence bundle ID (ev_...) to notarize. Bundle must have status \"complete\"."New value: +"Evidence bundle ID (ev_...) to notarize. Bundle must have status \"complete\". Example: \"ev_550e8400-e29b-41d4-a716-446655440000\""

First observedJun 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false and idempotentHint=true; the description goes well beyond that by disclosing gas cost (ETH), that the on-chain record is permanent and undeletable even after bundle purge, and how idempotency manifests (returns the existing attestation immediately). These are exactly the consequences an agent needs before committing an irreversible write.

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?

Front-loaded with the core action, then cleanly sectioned into PREREQUISITE, NOTE, Returns, and examples. Slightly long, and the Returns block plus three example prompts are somewhat redundant given an output schema exists, but each section is legible and earns most of its space.

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?

For a single-parameter, irreversible on-chain write, the description covers purpose, alternative, prerequisite, cost, permanence, and idempotent behavior. The output schema already carries return structure, so nothing an agent needs to invoke this correctly is missing.

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% and the single parameter already documents the ev_... format and the "complete" status requirement, so the schema does the heavy lifting. The description adds no syntax or format detail beyond it, making the baseline 3 appropriate.

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 and resource (notarize an evidence bundle) plus the exact mechanism (writing its manifest SHA-256 on-chain to Base/EVM). It explicitly distinguishes itself from verify_bundle, so 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 a clear when-to-use condition (need an immutable on-chain timestamp proving a document existed at a point in time), names the alternative (verify_bundle) for the cheaper path, and states the prerequisite (status must be "complete", check with get_bundle). Nothing is left to inference.

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?