Your Next Tours

Reorder Program Items

reorder_program_items

Idempotent

Reorder program stops. Params: id (uuid) + body { itemIds: [...] } -- ALL item ids, 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_program_items"
  }
}

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 / itemIds / maxItems
```
Added value: +2000
```
First observedOct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value by revealing the full-list replacement contract and the no-duplicates constraint, which the annotations do not convey. It stops short of saying what happens to existing items absent from the list.

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 compact fragments, front-loaded with the action and followed by the parameter contract; nothing is padding. The terse '--' notation and inline body literal are slightly cryptic but still parseable.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description covers the mutation's core contract; only edge-case behavior (unknown or missing ids, permission requirements) is left unstated.

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%, so the description must carry the meaning, and it does: id is identified as a uuid and body.itemIds as the complete ordered id list with no duplicates. It omits the schema's 2000-item cap, but that limit is already encoded in the schema.

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 program stops") that an agent can act on directly. It does not explicitly differentiate from adjacent siblings like reorder_program_info_cards or reorder_trip_items, relying on the 'program' scope to do that implicitly.

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?

Usage is implied by the verb, and "ALL item ids ... without duplicates" usefully signals a full-replacement rather than incremental edit. However, there is no explicit when-to-use vs. update_program_item or add_program_item, and no stated prerequisites such as ownership or permissions.

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?