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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get map event

get_map_event
Read-onlyIdempotent

Retrieve a map event's metadata and per-page settings—conditions, graphic, trigger, priority, movement—plus command counts, logic revisions, and a preview to inspect event behavior.

Instructions

Event metadata and every page's settings (conditions, graphic, trigger, priority, movement), command counts, logic revisions and a short preview.

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": {
      "mapId": "<mapId>",
      "eventId": "<eventId>"
    },
    "name": "get_map_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapIdYes
eventIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds return-content detail (counts, revisions, preview) that is useful since there is no output schema, but says nothing about size limits, behavior when mapId/eventId don't match, or whether 'short preview' is truncated. Adequate but not rich.

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 with no filler, and the highest-value content (event metadata, page settings) is front-loaded. The downside is that it is a verbless noun phrase and 'short preview' is left undefined, 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 correctly spends its words on return contents, which is the right instinct. However, for a two-parameter read tool with zero schema description coverage, the total absence of parameter explanation leaves a real gap an agent must guess at.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for mapId and eventId — yet neither is mentioned. It does not say that mapId scopes the map and eventId identifies the event within it, nor anything about valid ranges or invalid-ID behavior. The description does not compensate for the coverage gap.

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 enumerates the exact resource contents: event metadata, every page's settings (conditions, graphic, trigger, priority, movement), command counts, logic revisions, and a preview. The scope word 'every page's' implicitly separates it from single-page siblings like get_event_page, though no sibling is named. It lacks an explicit verb ('Retrieves...') but the resource is unambiguous.

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?

There is no statement of when to call this versus get_event_page, describe_map_event, get_event_logic, or list_map_events. The agent must infer from the name that this is the aggregate overview call. No prerequisites or exclusions are given.

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