Skip to main content
Glama

pdf_convert_markdown

Convert Markdown files into styled PDFs using CSS presets, custom CSS, page size, and orientation options for print-ready output.

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

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 behavioral burden but only says the output is "styled." It does not disclose that the call writes a file to the given output path, whether an existing file is overwritten, whether parent directories are created, or whether the operation is idempotent.

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 six-word sentence with zero filler, front-loaded with the core transformation. It is efficient, though so terse that brevity shades into under-specification rather than genuine conciseness.

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?

This is a six-parameter, file-producing tool with no annotations and no output schema, so the description is the only place to explain side effects and return behavior. It says nothing about the written file, overwrite semantics, or the styling options, which leaves an agent without what it needs to call the tool confidently.

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% and every parameter, including the five preset values and orientation, is already documented in the schema. The description adds only the word "styled," which loosely points at the preset/custom_css parameters but supplies no semantics, precedence, or defaults 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?

"Convert Markdown to styled PDF" states a specific verb (convert) and a concrete transformation between two named formats, so an agent knows exactly what it produces. It offers no differentiation from siblings such as md_to_pdf or html_to_pdf, which by name appear to overlap, leaving the agent to guess which conversion tool to pick.

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 when-to-use guidance, no prerequisites (e.g. input file must exist and be valid Markdown), and no mention of alternatives. Given the sibling list contains md_to_pdf, which sounds like the same operation, the absence of any routing hint is a real gap rather than a minor omission.

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