Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Detect signed-document tampering

document-trust_signed-tamper-detect

Compare current PDF hashes and ByteRange digests to caller-supplied expectations. Missing expectations are not invented. Price $0.04 USDC. POST /api/v1/document-trust/signed-tamper-detect. 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_signed-tamper-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
jsonNo
textNo
filesNo
signersNo
revocationsNo
certificatesNo
detachedSignaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does add real context: price ($0.04 USDC), a payment gate where unpaid calls return 402 and never execute, and the rule that absent expectations are not fabricated. It still omits whether the operation is read-only, what the response contains, and how large/multi-file inputs are handled.

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?

The purpose is front-loaded in the first sentence, followed by the constraint, price, endpoint, and payment behavior in short, waste-free clauses. Dense but appropriately sized for an API-style 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 8-parameter tool with nested object arrays, zero schema coverage, no annotations, and no output schema, the description leaves major parameter semantics undocumented. Pricing, the endpoint, and the 402 behavior are covered, but an agent still lacks enough information to populate most inputs 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?

Schema description coverage is 0% on a schema with 8 properties and nested arrays, so the description must compensate. It only touches the expectedSha256/expectedByteRangeSha256 concept via 'caller-supplied expectations' and says nothing about text, json, signers, revocations, certificates, detachedSignatures, or asOf.

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 precise verb and resource: 'Compare current PDF hashes and ByteRange digests to caller-supplied expectations.' That separates it from hash-computing or signature-verifying siblings. It never names a sibling tool as the alternative, though, so differentiation is inferred rather than stated.

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?

The sentence 'Missing expectations are not invented' subtly implies the tool only checks expectations you supply, which hints at when it applies. There is no explicit when-to-use vs. when-not guidance and no mention of alternatives like the signature-verify or coverage-check tools.

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