Skip to main content
Glama

Create a PDF

create_pdf

Turn Markdown or HTML you write into a well-set PDF: a report, invoice, letter, resume or plain document. Tables, headings, lists, images by URL and page breaks work; header, footer and page numbers are optional. For an invoice, resume or letter, prefer data (the fields, with template set to match): it is laid out properly, and an invoice is added up for you (leave out amounts, subtotal, tax or total to have them worked out; give them and they are checked). extract_data's invoice result can be passed as data as it is. Use it whenever the person wants a document they can download, print or send.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoInstead of markdown/html: the fields of an invoice, resume or letter (set template to match). We lay it out; for an invoice we also add up the lines, tax and total and report anything that doesn't add up.
htmlNo
styleNoquiet (default): modern sans, gray labels. classic: serif, fine rules, centered heads; suits letters and traditional CVs.
titleNoAlso the file name.
footerNo
headerNo
marginNo
markdownNo
templateNo
page_sizeNo
page_numbersNo

Output Schema

NameRequiredDescriptionDefault
cardNo
filesYes
stepsYes
job_idYes
statusYes
creditsYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedOutput schema / properties / files / items / properties / bytes / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / bytes / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / files / items / properties / download_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / download_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / files / items / properties / pages / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / pages / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / bytes_after / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / bytes_after / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / bytes_before / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / bytes_before / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / pages_after / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / pages_after / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / pages_before / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / pages_before / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: it discloses that in invoice mode the tool sums lines, tax and total, validates supplied figures, and reports mismatches, and that extract_data's invoice output can be piped in unchanged. That is real operational context an agent cannot get from readOnlyHint=false / destructiveHint=false. It stops short of saying where the PDF goes (job/file handle) or whether repeated calls create duplicates, which matters given idempotentHint=false.

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?

Front-loaded with purpose, then capability, then mode selection, then the use-case trigger — a sensible ordering. Dense but every sentence carries information; the parenthetical on invoice arithmetic is slightly repetitive with the data schema description in places, but no sentence is filler.

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?

For an 11-parameter tool with no required parameters and an output schema present, the description covers the branching shape of the call (markdown vs html vs data) which is the main failure mode an agent faces. It leaves layout knobs (margin, page_size, header/footer contents) undescribed, which is a modest gap since defaults will usually suffice.

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?

Schema description coverage is only 27%, with template, page_size, margin, page_numbers, header, footer, html, markdown and title largely undocumented, and the description compensates for the most important ones: the markdown/html/data tri-state, the need to pair data with a matching template, and which content features (tables, images, page breaks) render. It adds the data/template coupling that the schema does not state at the top level. It says nothing about margin, page_size or page break semantics, leaving four enum parameters to their bare names.

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?

Opens with a specific verb and resource ("Turn Markdown or HTML you write into a well-set PDF") and immediately enumerates the concrete artifacts it produces (report, invoice, letter, resume). The three input modes and their trade-offs are named, so an agent can distinguish this from conversion siblings like convert_to_pdf without reading 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?

Gives explicit selection guidance between its own input modes ("For an invoice, resume or letter, prefer data... with template set to match") and a clear trigger condition ("whenever the person wants a document they can download, print or send"). It never mentions the sibling convert_to_pdf or convert_from_pdf, so the agent must infer when to use this versus an existing-document conversion.

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.