Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Check document signature coverage

document-trust_signature-coverage-check

Measure ByteRange coverage over supplied PDF bytes for each signature field found locally. Price $0.03 USDC. POST /api/v1/document-trust/signature-coverage-check. 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_signature-coverage-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
jsonNo
textNo
filesNo
signersNo
revocationsNo
certificatesNo
detachedSignaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 valuable behavior: a $0.03 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. However, it says nothing about whether the operation mutates anything or is purely analytical, nor about timeouts or failure modes beyond the payment gate.

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?

Four short sentences, purpose front-loaded, with pricing and endpoint details compactly appended. No repetition and no wasted clauses; every sentence carries distinct information.

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 complex 8-parameter tool with no annotations and no output schema, the description should explain what the coverage result looks like and which inputs are required when. It covers billing behavior but leaves the analytical contract and input expectations substantially undefined.

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. 'Supplied PDF bytes' loosely maps to files.fileBase64, but signers, revocations, certificates, detachedSignatures, json, text, and asOf are undocumented in both places, leaving their format and purpose unexplained.

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?

States a specific verb and resource: 'Measure ByteRange coverage over supplied PDF bytes for each signature field found locally.' This is distinguishable from verification siblings like pdf-digital-signature-verify, though it never explicitly contrasts with them. The technical phrasing is precise but assumes familiarity with ByteRange and signature fields.

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?

No guidance on when to choose this over document-trust_pdf-digital-signature-verify, signature-timestamp-validate, or signed-tamper-detect, all of which operate on similar PDF inputs. The only conditional statement concerns payment (402), not tool selection. An agent must infer the use case from the name alone.

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