Skip to main content
Glama

pdf_remove_signatures

Remove digital signatures from PDFs by stripping signature fields, cryptographic locks, and widget annotations, producing a cleaned PDF ready for further processing.

Instructions

Remove Digital Signatures: Strip digital signature fields, cryptographic locks, and widget annotations. [Input: .pdf | Output: .pdf]

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_remove_signatures"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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, but it does disclose concrete destructive effects: signature fields, cryptographic locks, and widget annotations are removed. It omits irreversibility, permission/password requirements for encrypted PDFs, and failure behavior, leaving significant gaps for a mutation tool.

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?

A single front-loaded sentence enumerating the stripped elements plus a compact bracketed format tag; nothing is redundant, though the format tag is terse enough to be slightly cryptic.

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 a mutation tool with no annotations, no output schema, and two required parameters at 0% schema coverage, the definition leaves the agent without enough to call it confidently: path semantics, overwrite behavior, encryption handling, and post-removal validation are all unaddressed.

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?

Schema coverage is 0% and both parameters are bare strings, so the description must compensate. It does add the accepted format for each ('Input: .pdf | Output: .pdf'), but says nothing about whether these are file paths, whether output may overwrite input, or what produces an error.

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 verb and resource ('Remove Digital Signatures') and enumerates exactly what is stripped: signature fields, cryptographic locks, and widget annotations. That detail separates it from validation-style siblings, though no sibling is named 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 guidance, no mention of when removal is appropriate versus using pdf_validate_signatures first, and no prerequisites such as passwords for signed/encrypted documents. The agent must infer all of this.

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