Skip to main content
Glama

PDF в PNG

pdf_to_png

Конвертирует страницы PDF в PNG (без потерь, для схем и скриншотов). Результат — ZIP-архив. file_url: публичный URL PDF-файла. dpi: 72 | 150 (по умолчанию) | 300.

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_png"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiNo
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, it discloses two operationally important behaviors: the result is packaged as a ZIP archive, and the source must be available at a public URL. It also characterizes the output as lossless, and none of these claims conflicts with the supplied annotations.

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?

The purpose and ZIP result are front-loaded, followed by two compact parameter lines. Every sentence contributes useful information, with no filler or unnecessary repetition.

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 simple two-parameter converter, the definition covers the intended use, input requirement, valid DPI choices and default, and output packaging; the output schema further reduces the need to explain return fields. Explicit sibling routing and DPI selection advice would be refinements, but their absence does not prevent correct tool selection or 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?

With 0% schema description coverage, the description successfully documents both parameters: file_url must be a public PDF URL, while dpi accepts 72, 150, or 300 and defaults to 150. Additional advice about DPI's quality and file-size trade-off would help, but the parameters are already sufficiently specified for correct invocation.

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 opening sentence states a specific action and resource: converting PDF pages to PNG. The qualifiers "без потерь" and "для схем и скриншотов" help distinguish it from pdf_to_jpg, but that nearest sibling is never named or directly contrasted.

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 description gives concrete when-to-use context: choose this lossless PNG conversion for diagrams and screenshots. It does not explicitly say when not to use it or route photo-oriented use cases to pdf_to_jpg, so it falls short of fully explicit selection 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.