Skip to main content
Glama

pdf_to_pptx

Convert a PDF file into PPTX slides using best-effort slide generation for presentation workflows.

Instructions

Converts a PDF document to PPTX format via best effort slide generation.

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_pptx"
  }
}

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.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuinely useful behavioral trait — that slide generation is 'best effort', i.e. output quality is not guaranteed — but says nothing about whether the output path is overwritten, whether the input must be text-based versus scanned, or what happens on failure.

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?

A single front-loaded sentence with no filler; the format pair and the quality caveat both land immediately. It is efficient, though its brevity is partly a symptom of thin content rather than disciplined editing.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of behavioral information for a file-mutating conversion, yet it omits output-file semantics (overwrite/create), error behavior, and any fidelity expectations beyond a vague phrase. It is under-specified for the complexity of the operation.

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% with only two well-labeled parameters (input PDF path, output file path), so the schema already does the work. The description adds no format, path-convention, or constraint detail beyond it, which matches the baseline for full coverage.

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 names a specific verb and resource ('Converts a PDF document to PPTX format') and the target format alone separates it from siblings like pdf_to_docx and pdf_to_html. It stops short of explicitly contrasting itself with those siblings, so it is clear but not maximally differentiated.

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 conversion over pdf_to_docx, pdf_to_json, or other PDF outputs, and no prerequisites are stated. The only hint is the 'best effort' phrase, which implies low-fidelity output but does not tell the agent under what conditions the tool is or is not appropriate.

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