Skip to main content
Glama

Convert PDF to PDF/A

pdf_to_pdfa
Idempotent

Convert your PDFs to PDF/A-2b, the long-term archiving format many registries and online government services ask for, without changing how they look. Returns a link to download the result (kept about an hour). Credits on paid plans: 2 per page.

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": {
      "files": "<files>"
    },
    "name": "pdf_to_pdfa"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesInput files (.pdf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the return shape (a download link), link lifetime (~1 hour), and the credit cost model (2 per page on paid plans) — all of which matter for planning and follow-up calls. It does not address failure behavior or what happens when the expiry lapses, which keeps it below 5. Nothing contradicts the annotations: a conversion that writes a new file is consistent with readOnlyHint=false and destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the first front-loads purpose and format, the second front-loads the return value, retention, and cost. No filler, and the most decision-relevant facts come first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter conversion tool with no output schema, the description supplies what's needed to call and to interpret the result: target format, output as a link, link expiry, and cost. The absence of any note on failure modes or unsupported inputs is the only small gap.

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% for the single `files` parameter, so the URL vs name/content_base64 input modes and the 20 MB limit are already fully documented in the schema. The description adds no parameter-level detail beyond this, which is the baseline case rather than an above-baseline contribution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (convert) plus resource (PDF) and the exact target profile, PDF/A-2b, so an agent can distinguish it from the other conversion siblings like pdf_to_word or compress_pdf. It also conveys the 'without changing how they look' guarantee, which is the defining property of an archival conversion.

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

Usage Guidelines4/5

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

Gives a clear use context ('long-term archiving format many registries and online government services ask for'), which tells an agent when this conversion is the right choice over a generic one. It does not state exclusions or prerequisites (e.g., that input must already be a valid PDF, or when a different profile would be preferred), so it stops short of full routing guidance.

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