Skip to main content
Glama
Sign In
RPG Maker MZ Authoring MCP

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

clone event page

clone_event_page

Deep-copy an event page into the same or another event on a map, previewing the change set before commit. Use it to duplicate page logic without manual rebuilding.

Instructions

Clone a page (deep copy) into the same event or another event on the same map.

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>",
      "pageIndex": "<pageIndex>"
    },
    "name": "clone_event_page"
  }
}

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)
eventIdYesMap event ID
insertAtNo
pageIndexYesZERO-based page index (Page 1 in the editor = pageIndex 0)
allowScriptNotrue ONLY if the user explicitly asked to insert JavaScript (script commands, script conditions/operands, route scripts).
descriptionNoOptional description stored in the transaction log
destEventIdNo
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

A4/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, non-idempotent operation. The description adds meaningful behavior beyond that: it previews by default, returns semantic and native diffs with validation, and commits only when apply=true is used.

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 two short, front-loaded paragraphs with no filler. It first states what is cloned and where, then states the preview-first behavior and the commit shortcut.

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 nine-parameter mutation tool with annotations and no output schema, the description covers the essential clone target and preview/apply workflow, including what the preview returns. Minor gaps remain around insertion position, destination-event semantics, script handling, and warning acknowledgement, though most of those details are present in the schema.

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 78%, so the schema already documents most parameters, including apply, allowScript, acknowledgeWarnings, pageIndex, mapId, and eventId. The description reinforces the apply/preview behavior and implies the destination-event parameter, but it does not clarify the undocumented insertAt or destEventId parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: clone/deep-copy a page. It also defines the destination scope precisely, saying the copy can go into the same event or another event on the same map, which distinguishes it from page creation and move/reorder operations.

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?

It gives operational guidance for preview versus commit: default preview returns a change set, and apply=true commits when the preview is clean. However, it does not explicitly compare this tool with alternatives such as create_event_page or apply_changes, so the when-to-use-vs-alternatives guidance remains implied.

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