Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Pptx

create_pptx

Generate a native PowerPoint (.pptx) presentation from structured slide data, including titles, bullet lists, and optional speaker notes, then save it to a specified path.

Instructions

Create a native PowerPoint presentation (.pptx). slides is a list of slide dicts: {"title": str, "bullets": [str, ...], "notes": str (optional)}.

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": {
      "path": "<path>",
      "slides": "<slides>"
    },
    "name": "create_pptx"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
slidesYes
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It indicates a file-creating mutation but does not explain overwrite behavior, what happens if the path already exists, permissions, or other side effects; the output schema helps with return values but not mutation semantics.

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 is two tight sentences with the main action front-loaded and the complex slide structure explained compactly. Every sentence carries useful information without filler.

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?

The core creation behavior and slide object shape are covered, and the output schema can handle return-value documentation. Still, for a mutation tool with no annotations and no schema parameter descriptions, the missing path and overwrite semantics leave important invocation behavior under-specified.

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 0%, and the slides schema is generic, so the description adds meaningful structure for slides with title, bullets, and optional notes. However, path and overwrite are left unexplained, including what overwrite=true implies and how the default false affects existing files.

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: create a native PowerPoint presentation in .pptx format. The format distinguishes it implicitly from siblings such as create_docx, create_pdf, and create_excel, though no sibling is explicitly named.

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 or when-not-to-use guidance beyond the implied purpose of creating a PowerPoint file. It does not explain when to choose this over create_pdf or create_docx, nor does it mention prerequisites or overwrite conditions.

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

Deploy Server

Other Tools