Prince Cloud

markdown_to_pdf

Read-only

Convert Markdown content to PDF using Prince.

Args:
    content: Markdown content to convert
    style: Additional CSS to apply (inline stylesheet content)
    page_size: Page size (e.g., A4, letter)
    page_margin: Page margins (e.g., 20mm)
    javascript: Enable JavaScript execution
    pdf_profile: PDF profile (e.g., PDF/A-3b, PDF/UA-1)
    output_filename: Output filename for the PDF (default: "output.pdf")

Input Schema

TableJSON Schema

Name	Required	Description	Default
`style`	No
`content`	Yes
`page_size`	No
`javascript`	No
`page_margin`	No
`pdf_profile`	No
`output_filename`	No

TDQS

A4/5.0

Behavior3/5

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

Annotations already provide readOnlyHint and destructiveHint. The description adds behavioral context by naming the Prince engine and the JavaScript execution flag. But it doesn't describe return format or side effects (e.g., whether file is saved to disk), so partial transparency.

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 front-loaded with a clear main sentence and follows with a structured, concise Args list. Each parameter description is useful, though the list is somewhat long.

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?

The description covers parameters well but lacks explanation of the output format or file handling. No output schema exists, so this gap affects completeness. The tool is relatively simple but could state what the returned value is.

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

Parameters4/5

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

With zero schema description coverage, the description's Args section compensates well by providing meaningful descriptions for each parameter, including examples and defaults. It adds value beyond the schema's titles.

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 states 'Convert Markdown content to PDF using Prince' with a specific verb and resource. It clearly differentiates from sibling tools html_to_pdf and url_to_pdf by specifying Markdown as input format.

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 clearly implies usage for Markdown content, providing context. However, it does not explicitly mention alternatives or exclusions, like 'for HTML use html_to_pdf', so it falls short of a 5.

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

All Prince Cloud 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 distinctly different input source: HTML content, Markdown content, and a URL. There is no overlap in purpose, making selection unambiguous.

Naming Consistency5/5

All tool names follow the exact same verb_noun pattern: html_to_pdf, markdown_to_pdf, url_to_pdf. This is perfectly consistent and predictable.

Tool Count5/5

With only 3 tools, the server is tightly scoped to its core function of PDF conversion from three common input types. Each tool earns its place.

Completeness4/5

The set covers the most common conversion inputs (HTML, Markdown, URL). A minor gap is lack of direct file input, but these three cover the majority of use cases.

Resources

Need Help?