Skip to main content
Glama

md_to_pdf

Convert Markdown files into styled PDF documents using CSS presets, custom CSS, page size, and orientation settings for offline publishing and sharing.

Instructions

Convert Markdown to styled PDF

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "md_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to input file
outputYesPath to output PDF file
presetNoCSS preset (github, elegant, minimal, branded, compact)
page_sizeNoPage size format (e.g. A4, Letter)
custom_cssNoCustom CSS rules to apply
orientationNoPage orientation (portrait or landscape)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure and does very little with it. It does not say whether an existing output file is overwritten, whether directories are created, whether custom_css overrides preset styles, or what happens on failure, all of which matter for a file-writing conversion tool.

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 four-word phrase with no filler, and the key information is front-loaded. It is efficient to the point of under-specification given the tool takes six parameters, which keeps it from a 5.

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 six-parameter file-producing conversion tool with no annotations and no output schema, the description omits anything about overwrite behavior, style precedence between preset and custom_css, or the nature of the result. The schema covers parameter names, but the operational context an agent needs before invoking it is missing.

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

Parameters3/5

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

Schema coverage is 100%, so every one of the six parameters already carries its own description, and the baseline is therefore 3. The word 'styled' loosely signals that preset/custom_css affect appearance, but the description adds no precedence rules or format details beyond the schema.

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 names a specific verb ('Convert') and both source and target formats ('Markdown to styled PDF'), which cleanly separates it from siblings like html_to_pdf or img_to_pdf. It stops short of explicitly acknowledging those alternatives, so it does not reach a 5.

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 guidance on when to choose this over html_to_pdf or pdf_convert_markdown, nor any statement of prerequisites such as requiring an existing local Markdown file. The agent must infer the use case entirely from the name and phrase.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.