Skip to main content
Glama
Sign In
PDF-MCP

PDF-MCP

by Ceyhun-Tufan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pdf_from_markdown

Compile Markdown files or raw Markdown strings into styled, publication-grade PDF reports without JSON conversion. Supports frontmatter, sections, tables, code blocks, callouts, images, and lists.

Instructions

Compile a Markdown file (.md) or raw Markdown string directly into a styled, publication-grade PDF report without needing JSON conversion. Supports YAML frontmatter, # sections, ##/### Q&A headers, code blocks, | tables |, > [!NOTE] callouts, caption figures, and bullet points.

Input Schema

NameRequiredDescriptionDefault
themeNoVisual color theme (default: 'navy_blue').
titleNoOptional main document title (overrides YAML frontmatter or first # H1).
categoryNoCategory banner on cover (default: 'DOKÜMAN RAPORU').
metadataNoOptional key-value metadata pairs displayed at the bottom of the cover page.
subtitleNoOptional subtitle displayed on the cover page.
descriptionNoOptional overview / abstract displayed in the cover summary box.
output_pathYesFile path where the generated PDF document will be saved.
markdown_fileNoPath to a Markdown (.md) file to compile. Provide either 'markdown_file' or 'markdown_text'.
markdown_textNoRaw Markdown content string to compile. Provide either 'markdown_file' or 'markdown_text'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/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 supported Markdown constructs and that JSON conversion is unnecessary, but it omits key side-effect details such as whether output_path is overwritten, permission requirements, and error behavior.

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 description is a single front-loaded sentence that states the action first and then lists supported syntax. The feature list is dense but each item conveys real capability, with little wasted wording.

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

Completeness3/5

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

For a nine-parameter file-writing tool with no output schema, the description covers the input format and supported Markdown features adequately. It still lacks guidance on overwriting existing files, behavioral side effects, and explicit comparison with sibling tools, leaving notable gaps.

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 description coverage is 100%, so the schema already documents all nine parameters, including the theme enum and nested metadata object. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, 'Compile', and names the exact resource: a Markdown file or raw Markdown string turned into a PDF report. The phrase 'without needing JSON conversion' implicitly distinguishes it from the sibling pdf_generate_report tool, so an agent can identify its role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the supported input types: the tool is for Markdown-to-PDF compilation. However, the description does not explicitly state when to choose this over pdf_generate_report or other alternatives, nor does it give exclusions or prerequisites.

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

Deploy Server

Other Tools