Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Build document evidence bundles

document-trust_evidence-bundle-build

Bundle local signature, certificate, timestamp, tamper, coverage, and revocation checks with an explicit technical-vs-legal distinction. Price $0.07 USDC. POST /api/v1/document-trust/evidence-bundle-build. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "document-trust_evidence-bundle-build"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
jsonNo
textNo
filesNo
signersNo
revocationsNo
certificatesNo
detachedSignaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight: it discloses the price ($0.07 USDC), the payment gate (unpaid calls return 402 and do not run), and an important output caveat about the technical-vs-legal distinction. It omits whether the operation has side effects, what the returned bundle contains, and any size/rate constraints despite an 8-parameter input with large base64 payloads.

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?

Three tight sentences: capability first, then cost, then endpoint and failure mode. Every sentence carries information, though the raw POST path is arguably redundant with the tool name.

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?

For a tool with 8 parameters, deep nested arrays, no annotations, and no output schema, the description is thin. It never explains what the evidence bundle actually returns or how to populate the inputs, leaving the agent to infer structure entirely from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 top-level parameters containing many nested fields (files, signers, certificates, revocations, detachedSignatures, asOf, text, json). The description mentions none of them; only indirectly do the listed check types hint at the input families. An agent must read the raw schema to learn that, e.g., files carry fileBase64 and expectedSha256.

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 uses a specific verb ('Bundle') and enumerates the exact check families being combined: signature, certificate, timestamp, tamper, coverage, and revocation. An agent can tell this aggregates what the sibling tools do individually, though it never explicitly contrasts itself with them by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the aggregation of six check types suggests this is the tool to pick when you want everything in one evidence package rather than single-purpose checks like signature-coverage-check. No explicit when-to-use, when-not-to-use, or named alternative is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources