Your Next Tours

Reorder Slides

reorder_slides

Idempotent

Reorder slides. Params: id (uuid) + body { slideIds: [...] } -- ALL slide ids of the template, in the new order, without duplicates.

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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "reorder_slides"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`body`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes	Always true: the action succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026
- addedInput schema / properties / body / properties / slideIds / maxItems
```
Added value: +1000
```
First observedOct 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description reinforces that by framing the call as a whole-list replacement. It adds genuinely useful context beyond annotations — the no-duplicates and complete-set requirements. It does not say how invalid or partial lists are rejected, which keeps it below a 5.

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?

Two short sentences, the action front-loaded and the constraining detail immediately after. Only the 'id (uuid)' fragment is filler that repeats the schema.

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?

For a 2-parameter mutation with an output schema and full annotations, the definition covers the one behavior an agent could plausibly get wrong (sending a subset instead of the complete ordered list). Remaining gaps — error behavior on duplicates or unknown ids, and permission requirements — are minor given the structured fields already present.

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 description coverage is 0%, yet the description carries the crucial semantics the schema cannot: slideIds must be the complete set of slide ids in the new order with no duplicates, i.e. full-replacement rather than a partial move. It also clarifies that id refers to the template. The only weakness is that 'id (uuid)' merely restates the schema type.

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') and pins the target down with 'ALL slide ids of the template', which separates it from the reorder_* sibling tools that operate on program/trip items and info cards. It stops short of naming those siblings explicitly, so differentiation is implied rather than stated.

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 statement of when to use this versus the many reorder_* alternatives, nor any precondition such as needing an existing template with slides. The only guidance is the implicit 'supply the full ordered list', which is about invocation mechanics, not tool selection.

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

All Your Next Tours tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?