Skip to main content
Glama

pdf_validate_signatures

Cryptographically verify PDF digital signatures and certificate chains, check document integrity, and output JSON results with optional pre-sign tamper forensics.

Instructions

Validate Digital Signatures: Cryptographically verify digital signatures, certificate chains, and document integrity. [Input: .pdf | Output: .json]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_validate_signatures"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes
baselineNoCapture and report pre-sign incremental update tamper forensics / baseline integrity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that verification is cryptographic and covers certificate chains and integrity, and states the JSON output format, but says nothing about whether the operation is read-only, how failures are reported, or what happens with unsigned or malformed PDFs.

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?

Two compact sentences with the operation stated first and the format contract bracketed at the end; nothing is wasted. The header-style phrasing 'Validate Digital Signatures:' borders on restating the tool name, but overall it is tight and front-loaded.

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 3-parameter tool with no annotations and no output schema, the definition covers the core purpose and format but omits the shape of the validation result and the effect of the baseline flag. It is adequate to select the tool but thin on how to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 33%, only 'baseline' is documented in the schema (tamper forensics on pre-sign incremental updates). The description adds only the '[Input: .pdf | Output: .json]' format hint, leaving the semantics of the input/output path parameters and when to enable baseline largely to inference.

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 and resource ('Validate Digital Signatures') and enumerates the checks performed: cryptographic signature verification, certificate chain validation, and document integrity. This clearly separates it from generic 'pdf_validate' and from 'pdf_remove_signatures', though it never explicitly names those siblings.

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 by the specificity of the described checks; there is no statement of when to pick this over pdf_validate or what prerequisites exist (e.g., trusted root store, signed-but-untrusted certificates). An agent can infer the scenario, but the definition provides no explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.