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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Preview changes (batch)

preview_changes

Preview multiple event and database operations as one atomic change set, validate the resulting project state, and write nothing until you apply.

Instructions

Preview several operations as ONE atomic change set (cross-domain; any registered operation is accepted, so events and database records can be changed together). The whole resulting project state is validated; nothing is written until apply_changes. Operations: create_map_event, update_map_event, delete_map_event, create_event_page, clone_event_page, delete_event_page, update_event_page_settings, reorder_event_pages, update_common_event, create_event_from_template, append_event_blocks, insert_event_blocks, replace_event_block, remove_event_block, move_event_block, replace_event_logic, database_create_record, database_update_record, database_duplicate_record, database_delete_record, database_edit_collection, database_edit_note, database_set_class_curve.

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": {
      "operations": "<operations>"
    },
    "name": "preview_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNoCommit right after a successful preview (non-destructive operations only; needs --allow-write; warnings also need acknowledgeWarnings). Default false = preview only.
operationsYesOperations applied in order to one staged workspace
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

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the whole resulting project state is validated, that the operations are applied in order to one staged workspace, and that apply proceeds only after successful preview. It also notes that apply is non-destructive-only and that warnings require acknowledgement, adding useful safety context not fully captured by annotations.

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?

The core purpose is front-loaded in the first sentence, and the operation list is relevant context rather than filler. The list is long but directly supports correct invocation by naming accepted operations.

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?

With five parameters, high schema coverage, and no output schema, the description covers the essential workflow: preview first, validate the project state, then apply. It does not describe the preview response format or how errors/warnings are surfaced before apply, but the schema and apply semantics fill most of the gap.

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 the schema already documents the parameters, including apply, operations, allowScript, description, and acknowledgeWarnings. The description adds that operations are atomic and ordered but does not add syntax or format details beyond the schema.

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 uses a specific verb (preview) and clearly states the resource and scope: several operations as one atomic change set, cross-domain, with a concrete list of accepted operations. It distinguishes the tool from single-operation siblings by emphasizing batch atomicity and cross-domain acceptance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly indicates this is the preview step before apply_changes and that nothing is written until then. It implies use when multiple or cross-domain operations must be validated together, but does not explicitly contrast with preview_event_changes or database_preview_changes.

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