Skip to main content
Glama

Word в PDF

word_to_pdf

Конвертирует Word-документ (.doc/.docx) в PDF. file_url: публичный URL Word-файла.

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": "word_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the bar is lower. The description's useful addition is the access requirement that file_url must be publicly reachable, but it says nothing about file-size limits, timeouts, or how the converted file is returned.

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 short lines, front-loaded with the operation and followed by the one parameter that matters. Nothing is redundant and no sentence fails to add information.

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, so return values need not be described. For a single-parameter conversion tool the description covers the operation, the accepted input formats, and the input access constraint; only limits and error behavior are unaddressed.

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% — file_url is only typed as a string with no description — so the description must carry the semantics, and it does by explaining that the value is a public URL pointing to the Word file. It does not clarify whether a direct-download link is required versus a share-page URL.

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 Word document (.doc/.docx) into PDF, with the accepted input extensions spelled out. It implicitly separates itself from sibling word_to_jpg by naming the PDF target, though it never mentions that sibling or the other conversion tools directly.

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 implied by the format pair, and the description adds the practical requirement that the file must be available at a public URL. There is no explicit when-to-use/when-not guidance versus alternatives such as word_to_jpg or pdf_to_word.

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.