Skip to main content
Glama

HTML в PDF

html_to_pdf

Конвертирует HTML-файл в PDF. file_url: публичный URL HTML-файла. page_size: A4 (по умолчанию) | A3 | Letter. orientation: portrait (по умолчанию) | landscape.

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

Input Schema

NameRequiredDescriptionDefault
file_urlYes
page_sizeNoA4
orientationNoportrait

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond that: file_url must be a publicly reachable URL, implying no authenticated or local file access. It says nothing about size limits, timeouts, or whether the produced PDF is returned or stored.

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?

The purpose sentence is front-loaded and each subsequent line maps to exactly one parameter with no filler. The list style is terse but every line earns its place; nothing is redundant with the schema or title.

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?

Because an output schema exists, return values need not be explained, and the annotations cover mutability and open-world behavior. For a three-parameter conversion tool the description supplies the purpose, the required input constraint, and all option values, leaving only edge-case failure behavior undocumented.

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% and no enums are declared, so the description has to carry parameter meaning entirely, and it does: it identifies file_url as a public URL and enumerates the accepted values and defaults for page_size (A4 default, A3, Letter) and orientation (portrait default, landscape). Only file_url's format details (schemes, extensions, length limits) remain unspecified.

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 pair ('Конвертирует HTML-файл в PDF'), which unambiguously separates this tool from the other converters in the sibling list such as word_to_pdf, epub_to_pdf and xlsx_to_pdf. It does not explicitly name a sibling it is not, but the source format identity does the differentiation work.

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 guidance, no statement about when to prefer another converter, and no prerequisites beyond the implicit 'the input must be HTML'. The only contextual hint is that file_url must be a public URL, which is a constraint rather than usage guidance.

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.