Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Validate signature certificate chains

document-trust_signature-certificate-chain-validate

Parse supplied X.509 certificates and check validity windows and issuer links locally. Not a legal trust determination. Price $0.04 USDC. POST /api/v1/document-trust/signature-certificate-chain-validate. 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-certificate-chain-validate"
  }
}

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?

With no annotations, the description carries the full burden and does disclose key traits: processing is local, the result is not a legal trust determination, the cost is $0.04 USDC, and unpaid calls return 402 without executing. It does not describe the response shape or error behavior beyond the 402 case.

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, front-loaded with the actual operation and its scope limit before pricing and transport details. The endpoint path partially duplicates the tool name but is useful for HTTP invocation; nothing is padded.

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 says almost nothing about inputs, required combinations, or results. An agent knows the intent but not how to construct a valid call.

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, and the description explains none of them: asOf, json, text, revocations, signers, and detachedSignatures are left entirely to an undocumented schema. Only 'supplied X.509 certificates' loosely hints at the certificates array.

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 names a specific verb chain and resource: parse supplied X.509 certificates and check validity windows and issuer links, performed locally. The caveat 'Not a legal trust determination' scopes it against broader trust-reporting siblings, though no sibling is named directly.

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 rather than stated: the 'locally' and 'not a legal trust determination' framing suggests when this is appropriate versus a full trust report, but there is no explicit when-to-use, when-not, or named alternative among siblings such as revocation-status-check.

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