Skip to main content
Glama

sign_evidence_bundle

Cryptographically signs an evidence bundle with an Ed25519 keypair to attest authorship and detect tampering, helping verify bundle integrity before sharing.

Instructions

Cryptographically signs an evidence bundle using an Ed25519 keypair for author attestation and tamper detection.

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

Input Schema

NameRequiredDescriptionDefault
bundleIdYesThe unique identifier of the evidence bundle to sign.
privateKeyPemNoOptional Ed25519 private key in PEM format (uses local agent key if omitted).
workspacePathNoOptional workspace path hint.

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?

With no annotations supplied, the description does carry the full burden, and it does disclose the signature algorithm and that the result serves attestation and tamper detection. It is silent on the operation's side effects: whether the bundle is mutated or a signature is attached, whether signing is idempotent or irreversible, and what authorization or trusted-agent registration is needed.

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 front-loaded sentence stating verb, resource, algorithm and purpose with no filler. Nothing redundant and nothing buried.

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 three-parameter cryptographic mutation with no annotations and no output schema, the description covers what the tool is but not what an agent needs to invoke it safely. Missing are failure modes (unknown bundleId, absent or malformed key) and what the tool returns or changes, which the absent output schema means the description should have addressed.

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 each parameter (bundleId, privateKeyPem, workspacePath) is already documented in the schema, including the fallback to a local agent key. The description adds no further meaning about key handling, workspacePath's effect, or identifier format, so the baseline of 3 applies.

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 names a specific verb and resource ('Cryptographically signs an evidence bundle') plus the mechanism (Ed25519) and goal (author attestation, tamper detection), so the agent can tell this apart from capture/export siblings. It does not, however, clarify how it differs from near-neighbours like endorse_evidence_bundle or notarize_evidence_bundle, which are the most likely confusions.

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 when-to-use guidance, no prerequisite conditions (e.g., bundle must already exist, agent must be registered), and no reference to alternatives such as endorsing or notarizing. The agent must infer the routing decision entirely from the sibling names.

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