Skip to main content
Glama

pdf_to_pdf_a

Convert a PDF file to PDF/A format and save the archived version to a specified output path.

Instructions

Converts a PDF to PDF/A format. [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_to_pdf_a"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the PDF to convert to PDF/A.
outputYesPath to save the PDF/A file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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, yet it discloses only input and output file types. It says nothing about PDF/A conformance level (1b/2b/3b), whether transparency/fonts get altered, possible failure on non-compliant input, or what happens to existing artifacts.

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 short, front-loaded clauses with the action first and the I/O signature second. The bracketed Input/Output notation slightly duplicates what the schema already declares, but nothing is bloated or buried.

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 simple two-path conversion tool with no output schema, the definition covers the essentials. However, given zero annotation coverage, it should have closed the gap on conformance level, irreversible transformation of the source, and error conditions for a format conversion that can silently degrade a document.

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 description coverage is 100% and both parameters are fully documented as input path and output path, so the baseline is 3. The description adds nothing about path format, overwrite behavior, or extension requirements beyond what the schema already states.

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 (converts) and a specific target resource (PDF/A), which is a distinct archival target among the many pdf_to_* and *_to_pdf siblings. It stops short of explicitly contrasting itself with those siblings, but 'PDF/A' alone is enough to tell it apart from pdf_to_docx or pdf_compress at a glance.

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?

The description offers no when-to-use guidance — it never says to pick this when an archival/ISO-compliant document is required, nor does it mention any prerequisite or alternative (e.g., plain pdf_compress for size). The agent must infer selection purely from the format name.

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