Skip to main content
Glama

FB2 в PDF

fb2_to_pdf

Конвертирует книгу FB2 в PDF с оглавлением. file_url: публичный URL FB2-файла. 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": "fb2_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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false and idempotentHint=false, so the write/external-fetch profile is covered. The description adds two genuinely useful behaviors beyond that: the PDF is generated with a table of contents, and file_url must be a public URL (an access constraint the annotations don't express). It says nothing about cost, processing time, or how the resulting file is returned, which is acceptable since an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely compact — one sentence for purpose followed by a two-line parameter glossary — and the purpose is front-loaded. The terse key: value lines are efficient, though the lack of labels separating behavior from parameters makes it read as a fragment rather than structured guidance.

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 and annotations, this covers purpose, both parameters, allowed page values and the table-of-contents behavior. Remaining gaps (input size limits, output delivery) are minor given the output schema handles return values.

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%, so the description carries the full parameter burden and does so: file_url is defined as the public URL of the FB2 file, and page is given its allowed values (a5 default, book-like, or a4) even though the schema declares no enum. This is the exact information the agent needs before calling.

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 in Russian: 'Конвертирует книгу FB2 в PDF' (converts an FB2 book to PDF) plus an output characteristic ('с оглавлением' — with a table of contents). The source format FB2 implicitly distinguishes it from the epub_to_pdf, djvu_to_pdf and word_to_pdf siblings, though it never names them.

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?

No explicit when-to-use or when-not-to-use statement, and no prerequisites such as file size limits. Routing is only implied by the source format in the name and first sentence, which is adequate for a format-conversion tool but leaves the agent to infer the choice among conversion siblings.

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.