FileToPDF

Convert Markdown to PDF

convert_markdown

Render a raw Markdown string to a PDF, with optional CSS and layout options. A sensible default stylesheet is applied when no CSS is given. Costs 1 credit on success. Returns the PDF as an embedded resource.

Input Schema

TableJSON Schema

Name	Required	Description
`css`	No	Optional CSS to style the rendered Markdown (overrides the default stylesheet).
`pdfa`	No	PDF/A conformance level, e.g. "PDF/A-2b". (Pro/Scale/trial only.)
`pdfua`	No	Produce an accessible PDF/UA document.
`scale`	No	Render scale, 0.1–2.0.
`markdown`	Yes	The Markdown content to render.
`landscape`	No	Render in landscape orientation. (Pro/Scale/trial only.)
`marginTop`	No	Top margin in inches.
`save_path`	No	Optional absolute path to also write the PDF to on disk.
`marginLeft`	No	Left margin in inches.
`paperWidth`	No	Paper width in inches, or with a unit e.g. "210mm".
`marginRight`	No	Right margin in inches.
`paperHeight`	No	Paper height in inches.
`marginBottom`	No	Bottom margin in inches.
`userPassword`	No	Password required to open the resulting PDF.
`ownerPassword`	No	Owner password controlling permissions on the resulting PDF.
`printBackground`	No	Print background graphics/colors.
`nativePageRanges`	No	Page ranges to include, e.g. "1-3,5".
`preferCssPageSize`	No	Use the page size declared in CSS @page rules.

TDQS

A3.9/5.0

Behavior3/5

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

The description adds transparency beyond annotations by stating the cost (1 credit) and return type (embedded resource), and that a default stylesheet is applied. However, it does not disclose potential side effects (e.g., writing to disk via save_path) or required permissions. Annotations only provide openWorldHint, which is not contradicted, but the description is only partially transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of two sentences that front-load the core purpose and key details (defaults, cost, return). Every sentence adds value, with no redundancy.

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?

Given the tool's complexity (18 parameters, no output schema, minimal annotations), the description covers essential purpose and return type but lacks depth on layout options or parameter interactions. It is adequate but not exceptional for guiding an agent through all available features.

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?

With 100% schema description coverage, the parameters are already well-documented in the schema. The description adds a high-level summary ('optional CSS and layout options') but no new details beyond what the schema provides. Baseline 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 clearly states the tool renders a raw Markdown string to a PDF with optional CSS/layout options, using specific verbs and resources. It distinguishes itself from siblings like convert_html (HTML to something) and convert_file (file format conversion) by focusing on Markdown input and PDF output.

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

Usage Guidelines4/5

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

The description implies when to use this tool (Markdown to PDF) and mentions defaults (default stylesheet) and cost, but does not explicitly state when not to use it or provide alternatives. Context from sibling tools clarifies the niche, but direct guidance is missing.

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

All FileToPDF tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct input source: convert_file handles files from URLs, convert_html deals with raw HTML strings, convert_markdown processes Markdown, and get_account manages account info. There is no overlap.

Naming Consistency5/5

All tools follow a clear verb_noun pattern (convert_file, convert_html, convert_markdown, get_account), with consistent verb choice and naming style.

Tool Count5/5

Four tools is well-scoped for the domain: three conversion methods covering common input formats and one account tool. No tool is superfluous or missing.

Completeness4/5

The set covers the main conversion workflows (file URL, HTML, Markdown) and account management. Minor gaps like direct file upload or advanced formatting options for file conversion exist but do not hinder core functionality.

Convert Markdown to PDF

Input Schema

TDQS

Glama MCP Gateway

TDQS

Resources