Zovo Word to PDF

Convert Word to PDF

convert_word_to_pdf

Read-onlyIdempotent

Use this when the user uploads a Word .docx file and wants it as a PDF. Carries headings, paragraphs with alignment, bold, italic, underline, strikethrough, text sizes, links, bulleted and numbered lists with Word's numbers (decimal, letter and roman styles; other number styles print as digits and are listed as not carried), simple tables (merged cells, repeated header rows), JPEG and PNG images, page breaks, the page size and margins; footnotes and endnotes are printed at the end and tracked changes are accepted. Returns the PDF link, a read-back check of the PDF text, table cells, images and page size, and a list of each element type not carried (text boxes, shapes, charts, headers, footers, comments) with counts. Does not read .doc, password-protected or macro-enabled files, and does not keep fonts or colors. The link expires in about 1 hour.

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": {
      "file": "<file>"
    },
    "name": "convert_word_to_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes	The Word document to convert, e.g. report.docx (a .docx file up to 15 MB).
`page_numbers`	No	true (default) prints "page / total" centered at the bottom of each page; false prints no page numbers.

Output Schema

Name	Required	Description	Default
`page`	Yes
`check`	Yes
`notes`	Yes
`pages`	Yes
`counts`	Yes
`result`	Yes
`outline`	Yes
`downloads`	Yes
`file_name`	Yes
`not_carried`	Yes
`source_name`	Yes
`outline_count`	No
`expires_in_hours`	Yes
`carried_with_rule`	Yes
`replaced_characters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare the read-only, idempotent, non-destructive, closed-world profile, and the description adds substantial operational context beyond that: tracked changes are accepted, footnotes print at the end, unsupported element types are listed with counts, and the link expires in about an hour. Fonts and colors being dropped is exactly the kind of silent loss an agent needs to warn about before calling.

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 triggering condition is front-loaded and the long fidelity clause is dense but each element type named is a real expectation-setting detail. The middle sentence runs on with semicolons and parenthetical asides, so it could be split for faster scanning, but there is no filler.

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?

For a converison tool with a nested file object and an output schema, this covers the gaps that matter: accepted and rejected input formats, size limit implied by the schema, what survives conversion, what is dropped, and link lifetime. Return values are described only at a high level, which is appropriate given the output schema exists.

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 coverage is 100%, so file, file_id, download_url and page_numbers are already documented in the schema, and the description adds only the surrounding fidelity context (page size and margins carry over). It says nothing about the page_numbers toggle in prose, so no meaning is added beyond the schema.

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 concrete verb, resource and trigger: 'Use this when the user uploads a Word .docx file and wants it as a PDF.' This clearly separates it from the sibling inspect_word, which would report on the file rather than produce a PDF, without any schema reading required.

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 an explicit input condition (uploaded .docx) and exclusion list (.doc, password-protected, macro-enabled files) that tells the agent when the call will fail rather than succeed. It does not explicitly route to inspect_word when the user only wants to check contents, so the alternative path is left implicit.

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

All Zovo Word to PDF tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?