Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Check signature revocation status

document-trust_signature-revocation-status-check

Compare certificate serials to caller-supplied revocation entries only. Live commercial OCSP/CRL networks are not queried. Price $0.03 USDC. POST /api/v1/document-trust/signature-revocation-status-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-revocation-status-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.3/5.0
Behavior4/5

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

With no annotations, the description carries real load and does so: it discloses the billing model ($0.03 USDC), the transport (POST endpoint), the failure mode (unpaid calls return 402 and do not run), and a substantive behavioral boundary (no external OCSP/CRL network calls). Remaining gaps are what the response contains and how missing fields on the optional arrays are treated.

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 semantic constraint that matters most. The price and endpoint sentences are operational overhead but earn their place for billing-aware agents; nothing is padded or redundant.

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, zero-coverage, no-annotations, no-output-schema tool, the description explains only the central matching rule. It leaves the agent guessing which of the many optional inputs actually drive the comparison, how a match is reported, and what happens when revocations is empty.

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 coverage is 0% across 8 parameters, so the description must compensate and largely does not. It gestures at two of the eight top-level inputs (certificates as 'serials', revocations as 'revocation entries') but says nothing about files, json, text, signers, detachedSignatures, or asOf, nor about the fields inside revocations such as serialNumber, source, and revokedAt.

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 mechanism: 'Compare certificate serials to caller-supplied revocation entries only,' which tells the agent exactly what set of inputs is checked and against what. It is distinguishable from siblings like signature-certificate-chain-validate because it names its own data source, though it never says plainly 'determines whether signatures are revoked.'

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 phrase 'caller-supplied revocation entries only' and 'Live commercial OCSP/CRL networks are not queried' implicitly scope usage: this is for callers who already hold revocation data. There is no explicit when-to-use versus the sibling trust tools, and no statement of what to do if the caller has no revocation list.

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