Skip to main content
Glama

PDF в PDF/A

pdf_to_pdfa

Конвертирует PDF в PDF/A — формат долговременного хранения (архивы, суды, госорганы). file_url: публичный URL PDF-файла. version: 1 (PDF/A-1b) | 2 (PDF/A-2b, по умолчанию) | 3 (PDF/A-3b).

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

Input Schema

NameRequiredDescriptionDefault
versionNo2
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Beyond the annotations, the description discloses that the service must retrieve a publicly accessible source URL and that version 2 is selected by default. It does not discuss PDF/A validation strictness, conversion limitations, or source-file handling, leaving the behavioral context useful but modest.

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?

Three short lines front-load the conversion and its purpose, then document the two parameters without filler. The use-case examples and version mappings are compact and directly useful.

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

Completeness5/5

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

For a flat two-parameter conversion tool with an output schema, the description covers purpose, source accessibility, supported versions, and the default. Additional advice on choosing a PDF/A version or handling validation failures would be helpful, but its absence does not impede correct invocation.

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

Parameters5/5

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

Despite 0% schema description coverage, both parameters are documented: file_url must be a public URL to a PDF, and version is mapped to PDF/A-1b, PDF/A-2b, or PDF/A-3b with version 2 as the default. This supplies the essential invocation details missing from the schema.

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?

The opening sentence specifies the operation and resource precisely: converting PDF into PDF/A for long-term archival storage. This clearly distinguishes it from siblings such as pdf_to_word, repair_pdf, and flatten_pdf.

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?

The examples 'архивы, суды, госорганы' (archives, courts, government agencies) provide concrete situations where this conversion is appropriate. It does not explain when not to use the tool or name an alternative, so it falls short of explicit comparative 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.