Skip to main content
Glama

pdf-suite

pdf_from_html_text

Render HTML or plain text into a paginated vector PDF document using pdf-lib.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_from_html_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoHTML markup or plain text to render to PDF.
titleNoQuickCoderHub Document
outputPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that output is a paginated vector (not raster) PDF and that pdf-lib is the engine, but says nothing about where the file is written, whether existing files are overwritten, what is returned, or permission/limit constraints.

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?

A single efficient sentence with the core action and input forms front-loaded. 'Using pdf-lib' is implementation detail that occupies space but is short enough not to be harmful.

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

Completeness2/5

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

For a file-producing tool with no annotations and no output schema, the definition leaves critical gaps: it never explains the outputPath semantics (does it override a default? create directories? return the path?) and never describes the return value. An agent could invoke it but cannot predict side effects reliably.

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

Parameters2/5

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

Schema description coverage is only 33%, with only 'text' documented. The description mentions HTML-or-text rendering, which mostly repeats the existing schema text for that one parameter, and adds no meaning at all for 'title' or 'outputPath' — the latter being the most consequential unspecified parameter.

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 gives a specific verb+resource combination ('Render ... into a paginated vector PDF document') and names the accepted input forms (HTML or plain text), which distinguishes it from siblings like pdf_from_images. It does not explicitly name which sibling to prefer, but the input medium makes the distinction inferable.

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 mention of alternatives. The only usage signal is the implied one carried by naming HTML/plain text as the source, which leaves the agent to infer conditions on its own.

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.

Resources