Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Match signed contract versions

document-trust_contract-signed-version-match

Compare sha256 digests and version labels across supplied signed PDF copies. Differing hashes are reported, not invented. Price $0.04 USDC. POST /api/v1/document-trust/contract-signed-version-match. 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_contract-signed-version-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
jsonNo
textNo
filesNo
signersNo
revocationsNo
certificatesNo
detachedSignaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does a fair job: it states that mismatched hashes are reported rather than fabricated, discloses the $0.04 USDC cost, the POST endpoint, and that unpaid calls fail with 402 without executing. Gaps remain on return payload shape and on whether it performs any cryptographic signature verification versus pure digest comparison.

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, purpose front-loaded, no filler. Cost, endpoint, and payment-failure behavior are packed densely. Minor redundancy in restating the endpoint path as a full API route, but it aids callers.

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 an 8-parameter tool with no annotations, no output schema, and zero schema description coverage, the description is thin. It never explains the input shape (file list, signers, certificates, revocations, detached signatures) nor what a result contains beyond the presence of differing hashes, leaving the agent to reverse-engineer a complex payload unaided.

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 mentions version labels and sha256 digests, loosely mapping to versionLabel and expectedSha256, but leaves asOf, json, text, signers, revocations, certificates, and detachedSignatures entirely undiscussed. It also says 'PDF copies' while the schema accepts raw json/text inputs, adding confusion rather than clarity.

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?

Specific verb plus resource: 'Compare sha256 digests and version labels across supplied signed PDF copies.' An agent can tell this is a version/digest comparison operation rather than signature validation or tamper detection. Sibling differentiation is implicit rather than explicit, so it falls short of a 5.

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 only implied: the tool applies when you hold multiple signed copies and want to know if they diverge. There is no stated when-not condition and no named alternative among the many sibling verification tools. The prerequisite that calls must be paid is disclosed ('Unpaid calls return 402 and do not run'), which is useful selection context.

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