Skip to main content
Glama

pdf_sign

Digitally signs a PDF document to add a signature and saves the result to a new file. Use it to apply signatures locally without cloud services.

Instructions

Digitally signs a PDF document (Currently a stub). [Input: PDF (.pdf) | Output: PDF (.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_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the PDF to sign.
outputYesPath to save the signed PDF.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and the one thing it does disclose — that the tool is a stub — is genuinely important. Beyond that it says nothing: no indication of whether a certificate, key, or password is required, whether the signature is cryptographic or merely visual, whether existing signatures are preserved, or whether output overwrites input. That leaves the agent unable to predict the result of a call.

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 segments with the operation stated first and the stub caveat immediately after, so the most decision-relevant fact is front-loaded. The bracketed I/O line is a consistent convention rather than waste. Nothing superfluous, though the parenthetical is slightly buried mid-sentence.

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 two-parameter tool with a fully-described schema and no output schema, the definition covers what it does, the types involved, and the stub status. It is nonetheless thin on the operational requirements that make signing unusual — credentials/certificate source and whether the output is a new file or an in-place change — which matter even for a stub.

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 100%, so both parameters (input path, output path) are already documented in the schema with descriptions. The description adds nothing parametric beyond restating the PDF-to-PDF flow in the bracket notation, so the baseline 3 applies.

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: "Digitally signs a PDF document", which is clearly distinct from sibling operations like pdf_encrypt, pdf_change_permissions, or pdf_annotate. The bracket notation also declares the input and output types. It stops short of 5 because it doesn't explain how signing differs from superficially related siblings such as pdf_encrypt or pdf_fill_form.

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?

"Currently a stub" is an implicit warning that calls will not produce a real signature, which functions as a weak when-not-to-use signal. However, no alternative tool is named for the actual intent (e.g. protecting a document, adding a visible signature), and no prerequisites are stated. Usage is only implied by the verb.

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