Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_map_event

Retrieve specific event data from RPG Maker MZ/MV maps using map and event IDs to access game content for editing or integration.

Instructions

Get a specific event from a map

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYes
eventIdYes

Implementation Reference

  • The function retrieves a specific event from a map by calling getMapEvents and accessing the array index.
    export async function getMapEvent(
      projectPath: string,
      mapId: number,
      eventId: number
    ): Promise<MapEvent | null> {
      const events = await getMapEvents(projectPath, mapId);
      return events[eventId] || null;
    }
Behavior2/5

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

No annotations are provided, placing full burden on the description. While 'Get' implies read-only behavior, the description does not disclose error behavior (e.g., what happens if the event ID is not found), authentication requirements, or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence contains no wasted words, but the description is underspecified for the complexity of the context. It lacks front-loaded critical information needed to differentiate from siblings and compensate for missing schema documentation.

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

Completeness2/5

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

Given zero schema descriptions, no annotations, no output schema, and numerous sibling tools with similar names, the description provides insufficient context for an agent to confidently select and invoke this tool without additional trial and error.

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% for both parameters. The description provides minimal compensation: 'from a map' loosely implies mapId and 'specific event' implies eventId, but fails to define valid ID formats, ranges, or the hierarchical relationship between map and event.

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 specific verb ('Get') and resource ('event from a map') clearly identifying the operation. However, it fails to distinguish from sibling tool 'get_map_events' (plural), which likely returns a list versus this singular retrieval.

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?

No guidance provided on when to use this tool versus alternatives like 'get_map_events', 'search_map_events', or 'update_map_event'. The agent must infer the appropriate use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/garuh143/RPG-MakerMV-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server