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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get event logic (IR)

get_event_logic
Read-onlyIdempotent

Retrieves structured event logic with block IDs, revision token, and semantic completeness so you can inspect and safely edit RPG Maker MZ map, troop, or common events.

Instructions

The Event IR of a command list with block ids, the revision token required by path-based edits, and whether the semantic view is complete (raw_command blocks are opaque but preserved).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_event_logic"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapIdNoMap ID (map event page)
eventIdNoEvent ID (map event page)
troopIdNoTroop ID (battle event page)
pageIndexNoZERO-based page index (map event or troop page)
commonEventIdNoCommon event ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still contributes real behavior: it discloses that the returned semantic view may be incomplete because 'raw_command blocks are opaque but preserved'. That is exactly the kind of lossiness warning an agent needs before editing, though it says nothing about error cases or invalid identifier combinations.

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?

A single dense sentence that front-loads the payload (Event IR, block ids, revision token) with no filler. It is jargon-heavy ('IR', 'raw_command blocks') but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description helpfully sketches the return shape (block ids, revision token, completeness boolean). However, for a five-parameter tool with zero required parameters, it never explains how the map/event/troop/common-event selectors combine or which combinations are valid — a notable omission an agent would hit immediately.

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 coverage is 100% and all five parameters carry descriptions naming map/event/troop/common event and zero-based page index, so the baseline of 3 applies. The description adds nothing about which identifier selects which page type or that exactly one selector family must be supplied, so it does not go beyond the schema.

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

Purpose3/5

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

The description names the resource precisely ('Event IR of a command list') and enumerates what it carries (block ids, revision token, completeness flag), but it is a noun fragment with no verb, so the agent must infer that this is a retrieval operation. It also fails to distinguish itself from close siblings such as get_event_ir_reference or describe_event_page, which sound like they surface similar IR content.

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?

There is no explicit when-to-use statement and no sibling is named as an alternative. The phrase 'the revision token required by path-based edits' is the only usage signal, indirectly implying this tool precedes replace_event_logic-style edits, but the agent must connect that 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