Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Verify PDF digital signatures

document-trust_pdf-digital-signature-verify

Inspect PDF /Sig dictionaries and optional detached signatures locally. Technical verification is not legal enforceability. Price $0.05 USDC. POST /api/v1/document-trust/pdf-digital-signature-verify. 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_pdf-digital-signature-verify"
  }
}

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 carries the full burden, and it does disclose several behavioral facts an agent needs: processing is local, the call costs $0.05 USDC, it is a POST to a named endpoint, and unpaid calls return 402 without executing. It does not say whether the operation is read-only, what the response contains, or whether results are deterministic.

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 with the core capability front-loaded, followed by the scope caveat and operational details. The pricing and 402 lines are boilerplate but genuinely actionable for an agent deciding whether a call will execute, so little is wasted.

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 description is too thin: it never explains the input modes (raw json/text vs. uploaded files vs. supplied certificates and detached signatures) nor what verification verdicts come back. It covers cost and transport but not the substance of invoking the tool correctly.

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?

There are 8 top-level parameters with 0% schema description coverage, and the description explains none of them. It only loosely gestures at two of them via 'PDF /Sig dictionaries' and 'optional detached signatures', leaving asOf, json, text, signers, revocations, and certificates entirely undocumented in both the schema and the 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 uses a specific verb and resource: it inspects PDF /Sig dictionaries and optional detached signatures, and states this happens locally. That is far more precise than a restatement of the title, though it never names a sibling (e.g. revocation-status-check or timestamp-validate) to sharpen the boundary.

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 by 'Inspect PDF /Sig dictionaries and optional detached signatures' plus the scoping caveat that technical verification is not legal enforceability, which tells the agent not to over-claim results. There is no explicit when-to-use or when-not-to-use guidance relative to the many similarly named trust siblings.

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