Skip to main content
Glama
rcarmo

office-document-mcp-server

by rcarmo

pptx_duplicate_slide

Duplicate a slide including all shapes, tables, and formatting. Place the copy after the original or at the end of the presentation.

Instructions

Copy a slide including all shapes, tables, and formatting.

USE THIS when you need multiple slides based on a template slide. Performs a full XML deep copy so tables, images, and other shapes are faithfully duplicated.

Args: file_path: Path to the .pptx file slide_number: 1-based slide number to copy position: 'after' (right after original) or 'end' output_path: Optional output path (defaults to overwriting input)

Returns: Status with new slide number

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the .pptx file
slide_numberYes1-based slide number to copy
positionNo'after' (right after original) or 'end'
output_pathNoOptional output path (defaults to overwriting input)
Behavior3/5

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

Annotations already indicate mutation (readOnlyHint=false, destructiveHint=false). The description adds that it performs a 'full XML deep copy,' which is useful but doesn't disclose potential performance implications or other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description includes a summary, usage hint, and parameter list. However, the parameter section is redundant with the schema. It could be more concise by omitting the Args/Returns block.

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?

Given no output schema, the description includes 'Returns: Status with new slide number.' It explains the deep copy behavior. While it doesn't cover error cases, it is sufficiently complete for a duplicate tool with good annotations and schema.

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 coverage is 100%, so the schema already documents all parameters. The description repeats the same information (e.g., 'Optional output path (defaults to overwriting input)'), adding no new semantic value beyond what the schema provides.

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 clearly states 'Copy a slide including all shapes, tables, and formatting,' which is a specific verb and resource. It distinguishes from sibling tools like pptx_add_slide or pptx_import_slide by focusing on duplication.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'USE THIS when you need multiple slides based on a template slide,' providing clear usage context. It does not mention when not to use or alternatives, but the guidance is sufficient and not misleading.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rcarmo/python-office-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server