ChatPPT

Overview Schema Source Related Servers Discussions Admin

element_reorder

Reorder an element's z-index on a slide to bring it to the front, send it to the back, or move it forward/backward, controlling overlap and visibility.

Instructions

Reorder an element's z-index on a slide (bringToFront, sendToBack, bringForward, sendBackward).

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>",
      "slideId": "<slideId>",
      "elementId": "<elementId>",
      "action": "<action>"
    },
    "name": "element_reorder"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Z-order action
`deckId`	Yes	Stable ID of the presentation deck
`slideId`	Yes	Stable ID of the slide
`elementId`	Yes	Stable ID of the element to reorder

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and largely does not meet it. It does not say whether other elements' z-indices shift, whether the operation is idempotent at the extremes, what the response looks like, or what errors occur for an unknown element/slide. Only the mutation intent is conveyed.

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 sentence with the verb and resource front-loaded, followed by the parenthetical action set. Nothing is redundant or padded.

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 four-required-param mutation tool with no annotations and no output schema, the definition identifies the operation and its action space but omits side effects on sibling elements and failure conditions. Adequate to invoke, thin for predicting behavior.

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%, so every parameter (deckId, slideId, elementId, action) is already documented in the schema, including the action enum. The description restates the enum values without adding ordering semantics or constraints beyond them, so the baseline 3 applies.

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 an element's z-index on a slide') and enumerates the four z-order actions, which lets an agent distinguish it from the property-mutating element_update sibling. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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 action list implies the situations the tool covers (bring to front/back, nudge forward/backward), but the description never says when to prefer this over element_update or what preconditions apply (element must already exist on the slide). Usage is inferable rather than stated.

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