Skip to main content
Glama

PDF в Word

pdf_to_word

Конвертирует PDF в редактируемый Word-документ (.docx). file_url: публичный URL PDF-файла. ocr: скан без текста — распознать текст (русский и английский); до 100 страниц, цена — как у ocr_pdf.

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_url": "<file_url>"
    },
    "name": "pdf_to_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocrNo
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ocr
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safety profile (openWorld, not idempotent, not destructive), so the description's job is to add context, and it does: an OCR page cap of 100, pricing tied to ocr_pdf, and supported OCR languages (Russian and English). It leaves out file-size limits and the consequence of skipping ocr on a scanned file.

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?

Three short lines: purpose first, then per-parameter notes. No filler. The per-parameter lines could be formatted more explicitly, but nothing is wasted.

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?

An output schema exists and annotations cover safety, so the description only needs to cover inputs and cost/limits, which it does. Minor gaps are the lack of any input file size or scanned-PDF-without-ocr warning.

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 coverage is 0%, so the description must carry the parameters and it largely does: file_url is specified as a PUBLIC URL of the PDF, and ocr is explained as scan text recognition with language coverage and limits. Defaults (ocr: false) are left to the schema, which is fine.

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?

States a specific verb and both the source and target format: 'Конвертирует PDF в редактируемый Word-документ (.docx)'. That distinguishes it from siblings like pdf_to_txt, pdf_to_markdown and the reverse-direction word_to_pdf, though the description never names those siblings.

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?

Gives one useful conditional: use the ocr flag for scans without a text layer, cross-referencing ocr_pdf for price and limits. It does not say when to choose this tool over pdf_to_txt / pdf_to_markdown / pdf_to_pptx, nor what happens if a scan is converted without ocr.

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.