Skip to main content
Glama

Make a PDF

render_pdf
Read-onlyIdempotent

Render markdown as an A4 PDF. The PDF comes back inside this result as an embedded application/pdf resource (base64); nothing is stored and there is no download link. If you can run shell commands, save the file directly instead: curl -sS -X POST https://md2pdf.free/api/pdf -H "Content-Type: text/markdown" --data-binary @document.md -o document.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": {
      "markdown": "<markdown>"
    },
    "name": "render_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoclassic (default), modern or formal. Overrides any <!-- md2sign:style=... --> line.
markdownYesThe full markdown document. Start with "# Title": it names the file.
letterheadNoName in the formal style's letterhead band, e.g. a company name. Defaults to the document title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds important behavioral context beyond annotations: the PDF is returned as an embedded base64 application/pdf resource, nothing is stored, and there is no download link. It does not cover error handling or size limits, but the key output behavior is disclosed.

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 the core action and return behavior, then provides a practical alternative workflow. The curl command is verbose but directly relevant and actionable, though it makes the description longer than strictly necessary.

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

Completeness4/5

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

With only three parameters, full schema coverage, and no output schema, the description carries the important burden of explaining the return value. It does so by stating the PDF arrives as an embedded base64 resource and is not stored. Missing details about failure modes or size constraints are minor for this tool.

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 markdown, style, and letterhead. The description adds little parameter-level meaning beyond noting A4 rendering and does not clarify style or letterhead semantics beyond the schema. 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 opens with a specific verb and resource: render markdown as an A4 PDF. It is clearly distinct from sibling tools such as validate_markdown or send_for_signature, and an agent can identify the operation 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 Guidelines4/5

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

It gives explicit usage context and a preferred alternative: if shell commands are available, use curl to save the PDF directly instead. It does not discuss when to choose this over sibling tools like validate_markdown, but the rendering purpose is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.