KitchenSink4PPT

Overview Schema Source Related Servers Discussions Admin

Duplicate Slide

duplicate_slide

Deep-copy slides with full fidelity, cloning notes, charts, and embeddings while regenerating IDs to prevent corruption. Place the copy at any position with atomic save and backup.

Instructions

Deep-copy a slide: notes, charts with their embedded workbooks, and embeddings are cloned and retargeted; layout and media stay shared by design; creation GUIDs are regenerated (duplicates corrupt). slide: 0-based index or {"slide_id": N}. position: 0-based final index for the copy, default right after the original. The design pack adds move and hide: enable_tools(packs=['design']). Saves atomically with two-slot backup; backup=False skips rotation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slide`	Yes
`backup`	No
`position`	No
`file_path`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.1Sep 9, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / slide / title
```
Removed value: -"Slide"
```
First observedv1.0.0Aug 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the sparse annotations, the description discloses deep-copy semantics, GUID regeneration with a corruption warning, layout/media sharing, atomic save, and two-slot backup rotation. These are exactly the behavioral traits an agent needs to anticipate side effects.

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?

The paragraph is dense but efficient, front-loading the core action and parameter definitions. The enable_tools(packs=['design']) sentence is only loosely related to duplicating and adds slight noise, preventing a perfect score.

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

Completeness5/5

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

The description covers semantics, parameters, defaults, safety behavior, and backup handling; an output schema exists for return shape, and file_path is conventional. An agent has everything needed to invoke this tool correctly.

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?

With 0% schema description coverage, the description compensates for slide, position, and backup by defining formats and defaults. file_path is left unexplained, but it is a conventional self-evident parameter and the rest are well-specified.

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 opens with the specific action 'Deep-copy a slide' and clarifies scope by enumerating what is cloned (notes, charts, embedded workbooks, embeddings) versus shared (layout/media), which clearly distinguishes it from sibling insert/reorder/delete operations.

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?

It gives practical invocation context (slide index forms, position default, backup switch) that an agent can act on. It does not explicitly name sibling alternatives or state when not to use this tool, but the behavior described is unambiguous enough for selection.

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