Skip to main content
Glama

JPG в PDF

jpg_to_pdf

Конвертирует изображения (JPEG, PNG) в PDF. Каждое изображение — страница. file_urls: список публичных URL изображений.

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": "jpg_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare the operation is non-read-only, open-world and non-destructive, so the bar is lower. The description adds genuinely useful context beyond them: accepted input formats (JPEG, PNG, which is broader than the tool name suggests), the one-page-per-image output shape, and the requirement that URLs be public, which explains the openWorldHint. It omits operational limits (max images, size caps) and silent behaviors such as whether list order determines page order.

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 sentences, no filler, with the conversion purpose and the page-per-image behavior front-loaded before the parameter note. Every sentence carries information.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the annotations cover the safety profile. However, for a tool with a crowded sibling set and a single undocumented parameter, the description should address routing versus 'photo_to_pdf' and the ordering/multi-image semantics; it does neither, so it is adequate but incomplete.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the parameter, and it partially does by restating 'file_urls' as a list of public image URLs – the 'public' qualifier is real added meaning the schema lacks. It does not state whether ordering controls page sequence or whether mixed JPEG/PNG entries are allowed in one list, leaving the only parameter under-specified.

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 description names both the source and target formats and the unit of work ('Конвертирует изображения (JPEG, PNG) в PDF. Каждое изображение — страница'). That is a clear verb+resource, but it never distinguishes this tool from the near-duplicate sibling 'photo_to_pdf' (or from 'pdf_to_jpg' in the reverse direction), so an agent cannot route confidently between them from the description alone.

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?

There is no statement of when to use this tool rather than the alternatives, and no prerequisites are given. The page-per-image rule is a behavioral fact, not routing guidance, so the agent must infer the choice of tool from the name alone.

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.