Skip to main content
Glama

PDF в PowerPoint

pdf_to_pptx

Конвертирует PDF в PowerPoint (.pptx). Каждая страница — отдельный слайд. file_url: публичный URL 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_pptx"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Beyond the annotations, it discloses the important one-page-per-slide behavior and the need for a publicly accessible PDF URL. It remains unclear whether slide content is editable or pages are embedded as images, and no file-size, page-count, or URL-fetch limitations are mentioned.

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?

The description front-loads the conversion, then gives the page-to-slide behavior and input requirement without filler. Its compact parameter line is easy to scan and every statement contributes useful 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?

For a one-parameter converter with an output schema and behavioral annotations, this covers the essential selection and invocation details. Clarifying output editability or fidelity and any operational limits would make it more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema only declares an undescribed string, the description identifies file_url as a public URL to a PDF file. For the sole required parameter, this supplies both its resource meaning and the key accessibility constraint needed to invoke the tool correctly.

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?

The description specifies the operation, source, and target: converting PDF to PowerPoint (.pptx). "Каждая страница — отдельный слайд" further defines the conversion model, clearly distinguishing it from other PDF converters and the reverse pptx_to_pdf tool.

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?

The conversion direction and public-URL requirement imply the intended use and basic invocation prerequisite. However, there is no explicit when-not guidance, alternative-tool routing, or explanation of which conversion fidelity needs this tool serves best.

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.