Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Build electronic document trust report

document-trust_electronic-trust-report

Aggregate local signature, chain, timestamp, tamper, coverage, revocation, version, and multi-signer findings. Distinguishes technical verification from legal enforceability. Price $0.08 USDC. POST /api/v1/document-trust/electronic-trust-report. 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_electronic-trust-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
jsonNo
textNo
filesNo
signersNo
revocationsNo
certificatesNo
detachedSignaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral facts: price ($0.08 USDC), the POST endpoint, and that unpaid calls return 402 without running. It does not state the read-only/no-side-effect profile, whether the call is idempotent, how long an aggregation takes, or what happens when no artifacts are supplied (0 required params).

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?

Four short sentences, front-loaded with the capability before the cost and transport details. Dense and largely waste-free; the raw endpoint string is the only element of marginal value to an agent choosing the tool.

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 complex aggregator with 8 optional parameters, no output schema, and no annotations, the description covers the input domain and cost/failure behavior but leaves the returned report structure (finding categories, verdict fields) unspecified. Adequate to select the tool, thin for invoking it correctly with the right combination of artifacts.

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 parameters, so the description must compensate and largely does not. The listed check domains loosely hint at input groups (revocation data, certificates, signers, files), but terms like asOf, json, text, and detachedSignatures are never explained, nor is the relationship between supplied artifacts and which findings are produced.

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?

The description names a specific verb (aggregate) and enumerates exactly which findings are combined: signature, chain, timestamp, tamper, coverage, revocation, version, and multi-signer. That enumeration also implicitly differentiates it from the single-check siblings, and the added note that it separates technical verification from legal enforceability further pins down what the tool delivers.

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 implied rather than stated: an agent can infer this is the umbrella report to call instead of running the individual per-check siblings, and the legal-enforceability caveat signals the intended interpretation. However, no explicit when-to-use/when-not-to-use statement or named alternative appears, so the agent must infer the routing decision.

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