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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create event page

create_event_page

Adds a page to an RPG Maker MZ event, previewing the page definition and validation before committing changes. Use it to extend event logic with new conditions or blocks.

Instructions

Add a page to an event (appended by default). Remember: the engine activates the highest-numbered page whose conditions are met.

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

Input Schema

NameRequiredDescriptionDefault
pageNoEvent page definition: {settings?, blocks?}
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
insertAtNoZERO-based index to insert at (default: end)
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot convey: the default is a preview returning a change set with semantic and native diff plus validation, and apply=true is what commits. The note that the engine activates the highest-numbered page whose conditions are met is non-obvious runtime context.

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?

Two short paragraphs, front-loaded with the action and then the preview/commit contract. No restatement of the title, no filler, and the engine-activation note sits directly next to the operation it constrains.

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 an eight-parameter mutation tool with nested objects and no output schema, the description covers the essentials: what the default behavior returns (a change set with diffs and validation) and how to commit. The remaining risk information is delegated to schema fields like acknowledgeWarnings and allowScript, which are themselves well documented.

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 one of the eight parameters is already documented in the schema, making 3 the baseline. The description contributes only the implicit clarification that page creation appends by default, which complements rather than replaces the schema's insertAt 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?

"Add a page to an event (appended by default)" gives a specific verb (add) and resource (event page) plus a scope qualifier. The parenthetical about default append, contrasted with the insertAt parameter documented in the schema, distinguishes it from clone_event_page and reorder_event_pages, though no sibling is named outright.

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?

Guidance is about how to call the tool (preview then apply=true) rather than when to choose it over siblings such as create_event_from_template or clone_event_page. The two-step workflow is implied clearly, but the description never states when an agent should reach for this tool versus building a page from an existing template.

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