Skip to main content
Glama

markdown_to_pdf

Read-onlyIdempotent

Render caller-supplied text Markdown to a real downloadable PDF. Headings, paragraphs and lists; Windows-1252 text only. No images, HTML, fetches or external writes. Returns actual inline file bytes and SHA256. Official documentation: https://creora.darwin.so/providers/files/docs

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

Input Schema

NameRequiredDescriptionDefault
markdownYes

Output Schema

NameRequiredDescriptionDefault
artifactsYes
sheetNamesYes
sourceSha256Yes
externalWritesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds valuable constraints beyond annotations: Windows-1252 text only, no images/HTML/fetches/external writes, and returns inline bytes plus SHA256. This materially reduces misuse risk.

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?

Front-loads the action and artifact, then states restrictions and output in compact sentences. No repetitive filler; the docs link is the only optional extra.

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

Completeness5/5

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

The tool is simple, an output schema exists, annotations cover safety, and the description still states key content limits and return shape. Missing max input length is already in the schema, so nothing material is absent.

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?

Only one parameter exists (markdown), but schema description coverage is 0%. The description compensates by specifying caller-supplied text Markdown and Windows-1252 text only, though it omits the schema's 131072-character max. For a single obvious parameter, this adds useful semantic meaning but not complete coverage.

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?

States a specific verb (render) and target artifact (downloadable PDF) from Markdown, with clear input/output formats. Sibling tools convert other formats, so an agent can distinguish this 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?

The description gives clear context: caller-supplied Markdown text to PDF, with text-only/Windows-1252 and no image/HTML/fetch support. It does not name sibling alternatives or explicitly route between them, so it stops short of full when-to-use/alternative guidance.

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.

Resources