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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

move event block

move_event_block

Move an event block and its branches to a new position in the same list, adjusting indentation. Preview the change set first or apply it after validation.

Instructions

Move a block (with its branches) to another position in the same list; indentation is adjusted. Requires the list revision.

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": {
      "revision": "<revision>",
      "blockId": "<blockId>",
      "position": "<position>"
    },
    "name": "move_event_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNoCommit right after a successful preview (non-destructive operations only; needs --allow-write; warnings also need acknowledgeWarnings). Default false = preview only.
mapIdNoMap ID (map event page target)
blockIdYes
eventIdNoMap event ID (map event page target)
troopIdNoTroop ID (troop battle page target)
positionYesWhere to insert: {before:id} | {after:id} | {parentId, branch, index}. Inserting into the "else" branch of a conditional without one creates it.
revisionYesRevision token of the command list from get_event_logic / get_event_page (rejects stale block ids)
pageIndexNoZERO-based page index (map event or troop page)
allowScriptNotrue ONLY if the user explicitly asked to insert JavaScript (script commands, script conditions/operands, route scripts).
descriptionNoOptional description stored in the transaction log
commonEventIdNoCommon event ID (common event target)
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.2/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-idempotent, closed-world; the description adds genuinely useful behavior beyond that: a preview change set (semantic + native diff, validation) and that indentation is auto-adjusted when moving. It stops short of describing failure conditions or stale-revision handling, which would have earned a 5.

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 tight paragraphs: the operation and its side effect first, then the preview/commit contract. Every sentence carries information an agent needs before calling, with no filler.

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 12-parameter tool with a nested position object and no output schema, the description covers the mutation semantics, the return shape (change set with diffs and validation), and the commit gate. Remaining details (target-page selection, warning acknowledgement) live in the schema, which is nearly fully 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 92%, so the schema already documents revision, apply, position shape, and the various target IDs. The description only reinforces the revision requirement and the move semantics; it adds no new parameter-level detail beyond what structured fields provide.

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?

States a specific verb and resource ('Move a block (with its branches) to another position in the same list') plus the side effect of indentation adjustment. This clearly separates it from siblings like replace_event_block and remove_event_block without needing to open the schema.

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?

Explains the operational context: it needs the list revision, and it is preview-first with an explicit opt-in (apply=true) to commit when the preview is clean. It does not explicitly name a sibling alternative, but the move-vs-replace/remove distinction is implied by the description itself.

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