Skip to main content
Glama

DjVu в PDF

djvu_to_pdf

Конвертирует книгу или скан DjVu в PDF. file_url: публичный URL DjVu-файла.

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

Input Schema

NameRequiredDescriptionDefault
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 the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the bar is lower. The description adds that the service retrieves the file from a public URL, which is consistent with the openWorldHint and hints at server-side fetching, but it says nothing about size limits, failure modes, or processing cost.

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?

Two short lines: purpose first, then the single parameter's constraint. No filler, no repetition of the title, and the most important information 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?

An output schema exists, so return values need no explanation, and with only one required parameter the surface area is small. The definition covers purpose and input semantics adequately; missing only peripheral context such as limits or whether the source URL must be publicly reachable without authentication.

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 carry the parameter meaning — and it does, specifying that file_url is a public URL of the DjVu file, which conveys both format expectation and reachability requirement. It stops short of saying whether direct-download links, auth-protected URLs, or non-DjVu URLs are rejected.

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 pair: converting a DjVu book or scan into PDF. The named source format (DjVu) inherently separates it from the many sibling converters (epub_to_pdf, fb2_to_pdf, word_to_pdf), though it never explicitly acknowledges them.

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?

Provides no when-to-use or when-not-to-use guidance and names no alternative tool. The only usage constraint is implicit in the parameter note that the file must be a public URL, which tells the agent nothing about choosing this tool over other converters.

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.