Skip to main content
Glama
RPG Maker MZ Authoring MCP

RPG Maker MZ Authoring MCP

by NixonMSilva

reorder event pages

reorder_event_pages

Reorder an event's pages to change which active page takes priority, with a preview-first change set and optional immediate apply.

Instructions

Reorder pages: order lists current pageIndexes in their new order (a permutation). Changes which page wins when several are active.

Preview-first: returns a change set (semantic + native diff, validation). Pass apply=true to commit immediately when the preview is clean.

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": {
      "mapId": "<mapId>",
      "eventId": "<eventId>",
      "order": "<order>"
    },
    "name": "reorder_event_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNoCommit right after a successful preview (non-destructive operations only; needs --allow-write; warnings also need acknowledgeWarnings). Default false = preview only.
mapIdYesMap ID (from list_maps)
orderYes
eventIdYesMap event ID
allowScriptNotrue ONLY if the user explicitly asked to insert JavaScript (script commands, script conditions/operands, route scripts).
descriptionNoOptional description stored in the transaction log
acknowledgeWarningsNoAccept validation warnings when apply=true. Review them with the user first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive mutation. The description adds useful behavior beyond the annotations: preview-first execution, a returned change set with semantic/native diff and validation, and the effect on which page wins. It does not add much about permissions or idempotency, but the core mutation behavior is well disclosed.

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?

The description is compact and front-loaded: it starts with the action and the key parameter semantics, then explains the preview-first commit path. Every sentence carries useful information with no redundant wording.

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 7-parameter mutation with no output schema, the description provides enough context about preview behavior and the returned change set. The input schema covers most parameters in detail. A minor gap is that it does not route the agent among sibling preview/apply tools, but the definition is otherwise complete for correct invocation.

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 high at 86%, so the schema already documents most parameters. The description adds important meaning for `order` by explaining that it lists current pageIndexes in their new order as a permutation. That compensates for the order parameter lacking a schema description.

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?

The description uses a specific verb and resource: reorder event pages. It also clarifies the meaning of `order` and the effect of the reorder on active pages. It does not explicitly name sibling alternatives, but the purpose is clear.

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 description explains the preview-first workflow and states that `apply=true` commits immediately when the preview is clean. That gives conditional guidance for the apply step. It does not compare this tool to alternatives such as preview or apply tools, so usage guidance remains implied rather than explicit.

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

Deploy Server

Other Tools