Skip to main content
Glama

Фото в PDF

photo_to_pdf

Собирает фото с телефона в PDF: каждое фото — страница. HEIC с iPhone тоже. file_urls: публичные URL фото (JPG, PNG, WEBP, HEIC, TIFF, BMP), порядок = порядок страниц. page: a4 (по умолчанию, лист A4 в ориентации фото) | photo (страница по размеру фото). compact: уменьшить фото до 2000 px и убрать EXIF и геометку (по умолчанию да). grayscale: оттенки серого. scan: «Скан документа» — найти лист на фото, выровнять перспективу, белый фон. scan_color: bw (ч/б как скан, по умолчанию) | color — только при scan.

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_urls": "<file_urls>"
    },
    "name": "photo_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoa4
scanNo
compactNo
file_urlsYes
grayscaleNo
scan_colorNobw

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses real behavior: page order equals URL order, compact downscales to 2000 px and strips EXIF plus geolocation, and scan performs sheet detection and perspective correction. The metadata-removal effect is exactly the kind of consequence an agent would not learn from annotations alone; only file-count or size limits are absent.

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 is front-loaded in the first sentence, followed by a tight parameter-by-parameter list with no filler. Every line conveys either a format, a default, or a constraint.

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?

With an output schema present, return values need not be described, and the description covers formats, ordering, defaults, and the scan pipeline. It stops short of stating limits on file count or URL accessibility requirements beyond "публичные URL", which an agent building a batch call would want.

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?

Schema description coverage is 0% and the schema has no enums, so the description carries the full burden — and it does: it documents all six parameters, supplies the actual enum values (a4/photo, bw/color), states defaults, and explains the cross-parameter constraint that scan_color applies only with scan. This is materially more than the schema provides.

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 first sentence states a specific verb and resource ("Собирает фото с телефона в PDF: каждое фото — страница") plus the notable HEIC support, so an agent knows exactly what it produces. It does not differentiate from the sibling jpg_to_pdf, which also turns images into a PDF, leaving the agent to guess which of the two to call.

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 implied: "scan" and "scan_color" hint at the document-scanning scenario, and the multiple input formats suggest when this is preferable to a single-format converter. There is no explicit when-to-use/when-not statement and no mention of the jpg_to_pdf sibling as an alternative.

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.