Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Audit multi-signer documents

document-trust_multi-signer-audit

List PDF signature dictionaries and caller-supplied signers per document. Technical listing is not legal enforceability. Price $0.04 USDC. POST /api/v1/document-trust/multi-signer-audit. 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_multi-signer-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
jsonNo
textNo
filesNo
signersNo
revocationsNo
certificatesNo
detachedSignaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden, and it does disclose two real operational facts: the $0.04 USDC price and that unpaid calls return 402 without running. It says nothing about processing of uploaded PDFs (retention, size limits), what the audit compares signers against, or what the caller receives back, which are the traits an agent most needs for an 8-parameter ingestion tool.

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 compact sentences, front-loaded with the purpose, then the caveat, price, endpoint, and failure mode in descending order of importance. No filler, though the caveat and the endpoint/price lines could be merged without losing clarity.

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 undocumented parameters, no annotations, and no output schema, the definition covers only purpose, billing, and the 402 failure path. An agent cannot tell what the audit returns, how supplied signers are matched to dictionaries, or what the certificates/revocations inputs are meant to accomplish.

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. It names only two of the inputs conceptually (files as "PDF signature dictionaries" and the "caller-supplied signers"), leaving asOf, json, text, revocations, certificates, and detachedSignatures entirely undifferentiated between schema and prose.

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 opens with a specific verb and resource: "List PDF signature dictionaries and caller-supplied signers per document," which tells an agent exactly what the operation inspects. It adds a scope caveat ("Technical listing is not legal enforceability") but never contrasts itself with nearby tools like signature-coverage-check or revocation-status-check, so sibling differentiation is left implicit.

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 or when-not-to-use guidance and no named alternative, despite several siblings that also analyze signatures. The only steer is the negative caveat that a technical listing is not a legal enforceability judgment, which is a disclaimer rather than routing guidance.

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