Skip to main content
Glama
formfeed-dev

formfeed

Official
by formfeed-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Convert an office document to PDF

convert_to_pdf

Convert Word, Excel, PowerPoint, OpenDocument, RTF, or HTML documents to PDF, preserving original layout. Returns a downloadable PDF link without storing the file.

Instructions

Converts an existing Word, Excel, PowerPoint, OpenDocument, RTF or HTML document (up to 20 MB) to a PDF as it is, without filling in data, and returns the render with status and download_url. To make a document from a template and data, use render instead. Pass exactly one source: render_id, the render of a Word or PowerPoint template (output docx or pptx); path, a file on this machine; or file_base64 with file_name. Every call is a new render that counts units like a PDF; the Free plan cannot convert (Starter and above). The document is converted and not kept.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoAbsolute path of the document on this machine
filenameNoName of the PDF behind download_url, e.g. report.pdf
file_nameNoName of the document, e.g. report.xlsx; the type is read from the content
landscapeNoLandscape for spreadsheets and documents without their own page setup
render_idNornd_ id of a render whose output is docx or pptx, to get that document as a PDF
file_base64NoThe document to convert, base64 encoded; needs file_name
page_rangesNoPages to convert, e.g. 1-3,5; all pages when left out
single_page_sheetsNoEach spreadsheet sheet on one page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.10
    • changedInput schema / properties / file_base64 / description
      Previous value: -"The document, base64 encoded"New value: +"The document to convert, base64 encoded; needs file_name"
    • changedInput schema / properties / filename / description
      Previous value: -"Name of the PDF"New value: +"Name of the PDF behind download_url, e.g. report.pdf"
    • changedInput schema / properties / page_ranges / description
      Previous value: -"Pages to convert, e.g. 1-3,5"New value: +"Pages to convert, e.g. 1-3,5; all pages when left out"
    • changedInput schema / properties / path / description
      Previous value: -"Absolute path of a document on this machine"New value: +"Absolute path of the document on this machine"
    • changedInput schema / properties / render_id / description
      Previous value: -"rnd_ id of a render whose output is docx or pptx"New value: +"rnd_ id of a render whose output is docx or pptx, to get that document as a PDF"
  2. First observedv0.3.7

TDQS

A4.8/5.0
Behavior5/5

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

Annotations are all false (not read-only, not idempotent, not destructive), so the description carries the full burden. It discloses that every call creates a new render that counts units, that the Free plan cannot convert, and that the document is 'not kept.' It also specifies the output (render with status and download_url). No contradiction with annotations.

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 compact but information-dense, front-loading the core purpose and then covering alternatives, inputs, costs, and storage in a logical sequence. Every sentence earns its place; no fluff or repetition.

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?

Given 8 parameters, no output schema, and complex alternatives, the description covers the essential operational context: what inputs are allowed, what is returned, cost implications, and storage behavior. It lacks explicit detail on error conditions or status code meanings, but these are minor for a conversion tool with a sibling 'get_render' for retrieval.

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 100%, so baseline is 3. The description adds valuable semantic constraints not in the schema: exactly one source must be provided, and render_id must be from a Word/PowerPoint template. This goes beyond simple parameter names and justifies a 4.

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 a specific verb ('converts'), lists supported formats and size limit, and clearly differentiates from the sibling 'render' by saying 'To make a document from a template and data, use render instead.' The purpose is unambiguous and distinguishes the tool from all siblings.

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

Usage Guidelines5/5

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

It explicitly tells when to use this tool vs. render, and provides a critical constraint: 'Pass exactly one source' among render_id, path, or file_base64. It also clarifies plan eligibility and unit counting, which informs decision-making. This is complete usage guidance.

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

Deploy Server

Other Tools