Skip to main content
Glama
a951753abc

RPG Maker MZ MCP Server

by a951753abc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_event_commands

Adds multiple commands to an RPG Maker MZ event page by converting human-readable command objects into engine codes, with optional append or replace mode.

Instructions

Add commands to an event page. Commands use human-readable format that gets converted to RPG Maker MZ codes.

Supported command types:

  • show_text: { type: "show_text", face: "Actor1", faceIndex: 0, text: "Hello!" }

  • show_choices: { type: "show_choices", choices: ["Yes", "No"] }

  • transfer_player: { type: "transfer_player", mapId: 1, x: 5, y: 5 }

  • control_switches: { type: "control_switches", startId: 1, value: 0 } (0=ON, 1=OFF)

  • control_variables: { type: "control_variables", startId: 1, operationType: 0, operand: 0, value: 100 }

  • control_self_switch: { type: "control_self_switch", key: "A", value: 0 }

  • conditional_branch: { type: "conditional_branch", conditionType: 0, param1: 1, param2: 0 }

  • common_event: { type: "common_event", eventId: 1 }

  • change_gold: { type: "change_gold", operation: 0, value: 100 }

  • change_items: { type: "change_items", itemId: 1, operation: 0, value: 1 }

  • play_bgm: { type: "play_bgm", name: "Town1", volume: 90 }

  • play_se: { type: "play_se", name: "Decision1" }

  • wait: { type: "wait", duration: 60 }

  • fadeout_screen, fadein_screen, erase_event, game_over, return_to_title

  • comment: { type: "comment", text: "This is a comment" }

  • label/jump_to_label: { type: "label", name: "start" }

  • And many more (change_hp, change_exp, battle_processing, shop_processing, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYesMap ID
appendNoIf true, append to existing commands. If false, replace all commands.
eventIdYesEvent ID
commandsYesArray of command objects with "type" field
pageIndexNoPage index (0-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a genuinely useful trait: commands are authored in a human-readable form that 'gets converted to RPG Maker MZ codes.' However, it says nothing about mutation risk, whether append=false silently destroys existing page commands, whether indices shift, persistence, or failure modes.

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?

Purpose is front-loaded in the first sentence, and the long bullet block is reference material where each line earns its place by naming a command type and its payload shape. Slightly long, and the trailing 'And many more' is a mild hedge, but the structure is scannable.

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 tool whose core parameter is a polymorphic array of objects, the supported-type catalogue is exactly the missing documentation and it is supplied. The remaining gaps (append semantics, pageIndex behavior, how to discover unlisted command types) are covered by the schema or are minor. No output schema exists, so no return-value explanation is owed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description goes well beyond the schema by decoding the free-form `commands` array: it enumerates concrete command types with example payloads and field names (show_text, control_switches, change_gold, etc.). That is precisely the meaning an agent could not infer from 'Array of command objects with "type" field.'

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 first sentence gives a specific verb and resource: 'Add commands to an event page.' It is instantly clear this mutates event-page command lists rather than creating/updating the event itself. It does not, however, explicitly contrast itself with siblings like update_event or create_event, which an agent may also consider.

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?

The description never states when to reach for this tool versus create_event/update_event, nor any prerequisites (e.g., a loaded project, an existing page). The only usage-relevant signal is the implicit 'add commands' framing. The append-vs-replace decision, which is central to correct use, is left entirely to the schema.

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