Skip to main content
Glama

PDF в JPG

pdf_to_jpg

Конвертирует страницы PDF в JPEG. Результат — ZIP-архив (page-1.jpg, page-2.jpg...). 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_jpg"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiNo
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorld=true), so the description adds value by disclosing the output artifact (ZIP archive with per-page JPEGs) and the requirement that file_url be publicly reachable. It does not cover limits such as page count, timeouts, or what happens on partial failure, keeping it below a 5.

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: what it does, the output format, then parameter notes. Every line carries information not available elsewhere and the purpose is front-loaded.

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 two-parameter conversion tool with an output schema, both parameters are explained and the return artifact is described. The main missing piece is disambiguation from the nearest conversion sibling (pdf_to_png) rather than anything about the call itself.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden and mostly does: it explains that file_url must be a public URL and that dpi accepts 72, 150 (default), or 300 — the enum-like values and default are not in the schema at all. Minor gap: no guidance on which dpi to choose for which use case.

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 and resource ("Конвертирует страницы PDF в JPEG") and adds the concrete result format (ZIP with page-1.jpg, page-2.jpg). That clearly separates it from most siblings, but it never distinguishes itself from the close alternative pdf_to_png, which the agent must still infer.

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

Usage Guidelines3/5

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

Usage is only implicit in the verb and file-naming pattern; there is no statement about when to pick this over pdf_to_png, word_to_jpg, or image_to_text. The public-URL constraint on input is the only real prerequisite given.

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.