Skip to main content
Glama

notarize_evidence_bundle

Anchors an anonymized evidence bundle's SHA-256 digest to a remote transparency notary and stores the signed Ed25519 receipt for tamper-evident proof.

Instructions

Anchors only the anonymized bundle SHA-256 digest to a remote transparency notary service and stores the signed Ed25519 receipt.

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>",
      "notaryUrl": "<notaryUrl>"
    },
    "name": "notarize_evidence_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleIdYesThe unique identifier of the evidence bundle.
authTokenNoOptional Bearer authentication token for the notary endpoint.
notaryUrlYesHTTP or HTTPS URL of the transparency notary service.
timeoutMsNoOptional HTTP timeout in ms.
maxRetriesNoMaximum transient failure retry attempts with exponential backoff.
workspacePathNoOptional workspace path hint.
allowPrivateNetworkNoPermit local/private/loopback network notary targets (disabled by default for SSRF protection).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose valuable behavior: only a digest leaves the system (privacy), the call is remote/networked, and a signed Ed25519 receipt is persisted. It omits failure semantics, whether anchoring is irrevocable once notarized, and whether the receipt is returned or only stored locally.

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?

A single dense sentence with the scoping constraint front-loaded and zero redundant wording. Every clause (anonymized digest, remote notary, signed receipt) contributes distinct information.

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 7-parameter networked mutation with no annotations and no output schema, the description covers purpose and the local side effect but not return shape, error/retry behavior, or the security posture already captured only in the schema (allowPrivateNetwork/SSRF). Adequate but leaves real gaps for a tool with external side effects.

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 all seven parameters (bundleId, notaryUrl, authToken, timeoutMs, maxRetries, workspacePath, allowPrivateNetwork) are already documented in the schema. The description adds no parameter-level detail beyond implying a digest is derived from bundleId. Baseline 3 applies when the schema does the heavy lifting.

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 states a precise verb and object: it anchors 'only the anonymized bundle SHA-256 digest' to a remote transparency notary and stores a signed Ed25519 receipt. The word 'only' scopes it away from tools like sign_evidence_bundle or endorse_evidence_bundle, which operate on the bundle itself, so an agent can differentiate it without opening the schema. It stops short of naming an explicit sibling alternative.

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 statement of when to choose this over sign/endorse/verify siblings, nor any prerequisite (e.g., bundle must already exist and be hashed, notary must be reachable). The 'only' scope clause hints at usage but does not instruct. An agent must infer the trigger condition from the name alone.

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