Skip to main content
Glama

BRAINIAC Electronic Signature & Document Trust

Validate signature timestamps

document-trust_signature-timestamp-validate

Check PDF /M timestamps and caller-supplied signer signedAt values against asOf and optional certificate windows. Price $0.03 USDC. POST /api/v1/document-trust/signature-timestamp-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-timestamp-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
jsonNo
textNo
filesNo
signersNo
revocationsNo
certificatesNo
detachedSignaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 add genuinely useful operational facts: a $0.03 USDC price, the POST endpoint, and that unpaid calls return 402 without running. However it never states whether the operation is read-only, whether it mutates anything, or what the certificate-window evaluation means, so safety-critical behavior remains implied.

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?

Three short sentences, front-loaded with the core purpose, followed by pricing and payment-failure behavior. The endpoint URL is somewhat boilerplate but nothing is padded or vague.

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?

This is a complex tool with nested file, signer, revocation, certificate and detached-signature inputs, no annotations, and no output schema. The description does not explain input shapes, required combinations, or what a validation result conveys, so it is materially incomplete for the tool's complexity.

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 top-level parameters, so the description should compensate but only clarifies asOf, signers.signedAt and certificate windows. It says nothing about json, text, files, revocations, or detachedSignatures, leaving five of eight inputs undocumented anywhere.

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 states a specific verb and resource: check PDF /M timestamps and caller-supplied signer signedAt values against asOf and optional certificate windows. That is a concrete validation scope an agent can distinguish from revocation or chain validation siblings, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no routing to siblings like signature-revocation-status-check or signature-certificate-chain-validate. An agent must infer from the purpose alone whether timestamps need checking in a given flow.

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