Skip to main content
Glama

EPUB в PDF

epub_to_pdf

Конвертирует книгу EPUB в PDF с оглавлением. file_url: публичный URL EPUB-файла. page: a5 (по умолчанию, как книга) | a4.

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

Input Schema

NameRequiredDescriptionDefault
pageNoa5
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. The description adds two useful behavioral facts beyond them: the output PDF contains a table of contents generated from the EPUB, and file_url must be publicly reachable, which implies an external fetch. It does not mention conversion time, file-size limits, or failure behavior, which limits the added context.

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: a purpose sentence, followed by one line per parameter. The primary purpose is front-loaded, there is no filler, and the parameter notes are easy to scan.

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?

An output schema exists, so the description need not explain the return values, and both parameters are covered. For a two-parameter conversion tool with full annotations, this is close to complete, but it remains silent on input size limits, async/long-running behavior, and error cases for an unreadable URL.

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 must compensate, and it largely does: file_url is defined as the public URL of the EPUB file, while page is explained as a5 (default, book-like) or a4. It therefore adds meaning beyond the bare types and the enum-less string, though it does not say whether the page value is case-sensitive or what happens on invalid values.

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 states a specific verb and resource: 'Конвертирует книгу EPUB в PDF с оглавлением' (converts an EPUB book into a PDF with a table of contents). That is unambiguous about input and output format. It does not explicitly differentiate itself from the many sibling converters (fb2_to_pdf, word_to_pdf, html_to_pdf), though the name makes the input format obvious.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only implied guidance is that the source file must be an EPUB, which follows from the tool name rather than from the description itself. Nothing tells an agent what to do when the input is FB2, DJVU, or another sibling format.

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.