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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Describe event page

describe_event_page
Read-onlyIdempotent

Generates a human-readable summary of an RPG Maker MZ event page, covering conditions, graphic, trigger, priority, movement, and command flow with block IDs.

Instructions

Human-readable description of a page: conditions, graphic, trigger, priority, movement and the command flow with block ids.

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": "describe_event_page"
  }
}

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

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds useful context by listing what the human-readable output includes, especially command flow with block ids, but it does not disclose output format, length limits, or any behavior beyond content coverage.

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?

The description is a single front-loaded sentence with no wasted words. It efficiently states the output type and enumerates the most important contents.

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?

For a tool with five optional identifiers and no output schema, the description usefully summarizes what will be described. It stops short of explaining valid parameter combinations for map event, battle event, and common event pages, and does not clarify when to use this rather than get_event_page.

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 all five parameters are already documented in the input schema. The description adds no guidance on how to select between mapId/eventId, troopId, commonEventId, and pageIndex, which is a meaningful ambiguity given that all parameters are optional, but the high schema coverage sets the baseline at 3.

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 description uses a clear verb ("describe") and resource ("event page") and enumerates the page aspects covered: conditions, graphic, trigger, priority, movement, and command flow with block ids. It does not explicitly distinguish itself from close siblings like get_event_page or describe_map_event, but the purpose is specific enough to select correctly.

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?

The implied usage is when an agent needs a human-readable summary of an event page rather than raw page data. However, it gives no explicit when-to-use guidance, no exclusions, and does not mention alternatives such as get_event_page or analyze_event_flow.

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