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

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Describe map event

describe_map_event
Read-onlyIdempotent

Describe a map event and all its pages in human-readable form, with page priority explained, so you can inspect event behavior before modifying an RPG Maker MZ project.

Instructions

Human-readable description of an event and ALL its pages (page priority explained).

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

Input Schema

NameRequiredDescriptionDefault
mapIdYes
eventIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds that output is human-readable prose covering every page and that page priority is explained, which is real context beyond the annotations, but it says nothing about length, ordering, or what happens when the event has no pages.

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?

One tightly written sentence with the key scope qualifier ('ALL its pages') front and center. The parenthetical about page priority is slightly compressed but earns its place by telling the agent what the output explains.

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 two-parameter read tool with a full annotation set and no output schema, the description is almost adequate, but it leaves the return payload shape and the meaning of the two required IDs unaddressed. It is the minimum viable definition rather than a complete one.

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 it never mentions either parameter or their relationship. An agent must infer from names alone that eventId is scoped to mapId.

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?

States a specific verb (describe) and resource (map event plus all of its pages), and the capitalized 'ALL its pages' distinguishes it from the single-page sibling describe_event_page. It does not explicitly contrast with get_map_event, so the boundary with that raw-data sibling is left implicit.

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?

Usage is only implied: the emphasis on 'ALL its pages' suggests this is the whole-event overview when you don't want one page at a time. There is no explicit 'use this instead of get_map_event when...' guidance or any stated prerequisite such as needing a valid mapId/eventId pair.

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