Skip to main content
Glama

pdf_to_docx

Convert a PDF document into a DOCX file by extracting its text, enabling Word-compatible editing and reuse.

Instructions

Converts a PDF document to DOCX format by extracting its text.

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_to_docx"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output file path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose a key behavioral trait: conversion happens 'by extracting its text', which signals that images, tables and layout will not survive. It says nothing about overwrite behavior, missing input files, scanned PDFs, or error conditions, which are significant gaps for a file-writing tool.

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?

A single sentence with zero filler, front-loading the verb and the resource before the extraction detail. Nothing could be removed without losing information.

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

Completeness3/5

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

For a simple two-parameter converter with a fully documented schema, the definition is nearly adequate, but the absence of annotations means the description should say more about failure modes and output-side effects. It stops short of what an agent needs in order to handle errors or confirm the file was written.

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%, so both the input PDF path and output file path are already documented. The description adds no further meaning about path formats, relative vs absolute paths, or whether directories must exist; the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: converting a PDF document to DOCX format. The target format implicitly distinguishes it from siblings such as pdf_to_markdown or pdf_to_html, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over alternatives like pdf_to_markdown or pdf_to_json, and no prerequisites such as file existence or write permissions are mentioned. The only implied usage is the obvious need for a DOCX output.

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