Skip to main content
Glama

pdf-suite

pdf_to_pdfa_archival

Normalize a PDF for long-term ISO-19005 PDF/A-like archival consistency by flattening forms, embedding standard fonts, and setting XMP/catalog timestamps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_to_pdfa_archival"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNo
base64DataNo
outputPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does disclose the transformations performed (form flattening, font embedding, timestamping), which usefully hints that form interactivity is destroyed. However, it never states whether files are rewritten in place or written to a new path, whether the original is preserved, or whether output can be validated.

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 that lists the concrete operations in a natural order with no filler. Dense but readable; the only cost is that the compression into one clause leaves the ambiguities above unresolved.

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 document-mutating tool with no annotations, no output schema, and fully undocumented parameters, the description omits the operational essentials: which input parameter to supply, where output lands, and whether the source file is modified. What is present is accurate but insufficient for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, and the description adds no meaning about inputPath vs base64Data (two alternative input sources) or outputPath. It also ignores that zero parameters are marked required even though an input is obviously needed, leaving the agent to guess the input/output contract.

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?

Names a specific verb (normalize) and resource (PDF) plus the goal (long-term ISO-19005 archival consistency) and the three concrete actions taken. It is distinguishable from siblings like pdf_compress or pdf_compliance_audit, though the hedge 'PDF/A-like' introduces ambiguity about whether real conformance is claimed.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternatives. The phrase 'long-term archival' implies the scenario but an agent must infer whether this is the right tool versus pdf_compliance_audit or pdf_compress.

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