ChatPPT

Overview Schema Source Related Servers Discussions Admin

slide_move

Reorder presentation slides by setting a complete slide order or moving one slide to a target position in a deck.

Instructions

Reorder slides in a presentation deck, either by providing a complete slideOrder array or moving a single slideId to a target position.

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": {
      "deckId": "<deckId>"
    },
    "name": "slide_move"
  }
}

Input Schema

Name	Required	Description
`deckId`	Yes	Stable ID of the presentation deck
`slideId`	No	Single slide ID to move
`slideOrder`	No	Complete array of slide IDs declaring the desired final order
`toPosition`	No	0-based target index when moving a single slide

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

A3.6/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 behavioral burden. It discloses the either/or operating modes, which is real context, but says nothing about permissions, whether the reorder is atomic, what happens if slideOrder omits existing slides, or what occurs if both slideId/toPosition and slideOrder are provided.

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?

A single well-formed sentence with the action front-loaded and the two modes following; no filler and nothing redundant.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers the core mechanism but leaves key operational constraints unstated, notably whether slideOrder must be a complete permutation of all slides and how conflicting parameters are resolved.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds genuine value by framing slideOrder and slideId+toPosition as alternative input strategies rather than independent parameters. It does not clarify the exhaustiveness requirement of slideOrder or the interaction when conflicting inputs are passed.

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 ('Reorder slides in a presentation deck') and immediately names the two supported modes. It is clearly distinct from element_reorder and slide_update by resource and action, though it never explicitly contrasts itself with those siblings.

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 two modes imply when each applies (bulk reorder vs. single slide move), but the description never states that they are mutually exclusive, which combination of parameters each mode requires, or when to prefer one over the other. Usage must be inferred from the schema.

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