Skip to main content
Glama

Convert Word to PDF

word_to_pdf
Idempotent

Convert Word (DOCX, DOC), OpenDocument (ODT) and RTF documents into PDFs ready to send or print. Returns a link to download the result (kept about an hour). Credits on paid plans: 10 per file.

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": {
      "files": "<files>"
    },
    "name": "word_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesInput files (.doc, .docx, .odt, .rtf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare idempotent=true, destructive=false, and openWorld=true, so the safety profile is covered. The description adds genuinely new behavior: the output is a download link that expires after about an hour, and paid plans are charged 10 credits per file. It stops short of saying whether authentication is required or what happens on conversion failure.

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?

Two tight sentences: formats and outcome first, then the return value and cost. Every clause carries information an agent would otherwise lack, with no 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?

With only one parameter at full schema coverage and no output schema, the description fills the main gaps by explaining the return value (a temporary download link) and the cost model. It does not address failure modes or file-size constraints beyond what the schema already states, which is a minor omission for a tool this simple.

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%, and the schema itself already lists the accepted extensions and the 20 MB base64 limit. The description only restates the supported formats, adding no new meaning such as per-file behavior or error semantics for the files array. Baseline 3 is appropriate when the schema carries the parameter detail.

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 and resource: convert Word/DOC/ODT/RTF documents into PDFs. The direction of conversion is unambiguous, so an agent can immediately distinguish it from the inverse sibling pdf_to_word without opening either schema.

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

Usage Guidelines3/5

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

Usage is only implied by the conversion direction; there is no explicit when-to-use or when-not guidance, and no alternatives are named. The credit note ('10 per file on paid plans') does give a weak signal that multi-file batches are possible, but it is not framed as 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