Skip to main content
Glama

PowerPoint в PDF

pptx_to_pdf

Конвертирует презентацию PowerPoint (.pptx/.ppt) в PDF. file_url: публичный URL PPTX-файла.

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

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, destructiveHint=false and idempotentHint=false, covering the safety profile. The description adds one genuinely useful behavioral constraint that annotations do not convey: the file must be reachable via a public URL. It says nothing about processing time, file size caps, or failure modes for private/unreachable URLs.

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, conversion purpose front-loaded, parameter note second. Nothing redundant and nothing padded.

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?

An output schema exists, so return values need not be explained, and the single-parameter surface is small. However, for an open-world network tool the definition omits practical constraints an agent would want (size limits, public-URL reachability expectations, and the minor .ppt vs 'PPTX-файл' wording inconsistency).

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 a bare untyped string with no description — so the description carries the whole burden and does so meaningfully: it tells the agent the value is a public URL pointing at a PPTX file. It stops short of format specifics (URL scheme, auth, accepted extension mismatch between .ppt/.pptx in prose and 'PPTX-файл' in the param note).

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 resource pair ('Конвертирует презентацию PowerPoint ... в PDF') with explicit input formats (.pptx/.ppt) and output format. The direction of conversion clearly separates it from the sibling pdf_to_pptx, 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 when-to-use guidance, no mention of when to prefer pdf_to_pptx or another converter, and no prerequisites such as size limits or authentication. Usage is only inferable from the tool name and the conversion statement.

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.