Skip to main content
Glama

endorse_evidence_bundle

Appends a cryptographically signed peer review endorsement to an evidence bundle, capturing the reviewer's role, verdict, and comment so approvals stay tamper-evident.

Instructions

Appends an independent, cryptographically signed peer review endorsement to an evidence bundle.

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>",
      "agentId": "<agentId>",
      "role": "<role>",
      "verdict": "<verdict>",
      "comment": "<comment>"
    },
    "name": "endorse_evidence_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesReviewing agent professional role.
agentIdYesUnique identifier of the reviewing agent (e.g. "agent:tester-v1").
commentYesDetailed evaluation commentary supporting the verdict.
verdictYesReview endorsement verdict.
bundleIdYesThe unique identifier of the evidence bundle to endorse.
privateKeyPemNoOptional PEM-encoded private key for signing endorsement.
workspacePathNoOptional workspace path hint to locate the bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation appends a signed endorsement, but does not explain permission requirements, whether the append is irreversible, how the optional privateKeyPem affects signing, or what the tool returns after endorsement.

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?

The definition is a single front-loaded sentence that identifies the action, resource, and key properties without unnecessary wording. Nothing is repeated or padded.

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

Completeness2/5

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

This is a mutating, cryptographically signed operation with seven parameters, no annotations, and no output schema, so the description should carry substantial behavioral context. It is too thin for that burden, leaving signing behavior, preconditions, and post-call effects unexplained.

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 are already documented in the input schema. The description adds no parameter-level meaning beyond what the schema provides, which establishes the baseline score of 3.

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 specific verb and resource: appending a peer review endorsement to an evidence bundle, including that it is independent and cryptographically signed. It does not distinguish this operation from nearby siblings such as sign_evidence_bundle or add_assertion, so an agent gets a clear purpose but no sibling routing.

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 explicit guidance on when to use this tool versus sign_evidence_bundle, notarize_evidence_bundle, add_assertion, or verify_evidence_bundle. Usage is only implied by the name and the phrase 'peer review endorsement'.

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