Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

create_map_event

Add interactive events to RPG Maker MZ/MV maps by specifying map coordinates, event name, and behavior pages for game development.

Instructions

Create a new event on a map

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYes
nameYes
xYes
yYes
noteNo
pagesYes

Implementation Reference

  • The createMapEvent function handles creating a new map event by loading the map file, calculating the next available event ID, adding the event, and saving the map data back to the JSON file.
    export async function createMapEvent(
      projectPath: string,
      mapId: number,
      eventData: Omit<MapEvent, 'id'>
    ): Promise<MapEvent> {
      const map = await getMap(projectPath, mapId);
    
      // Find the next available event ID
      const maxId = map.events.reduce((max, event, index) => {
        return event && index > max ? index : max;
      }, 0);
    
      const newEvent: MapEvent = {
        id: maxId + 1,
        ...eventData
      };
    
      map.events[maxId + 1] = newEvent;
    
      const mapPath = getMapPath(projectPath, mapId);
      await writeJsonFile(mapPath, map);
    
      return newEvent;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a mutation operation, the description provides no details about side effects (what happens if coordinates x/y are already occupied), idempotency, whether the operation is reversible, or the structure/contents expected in the 'pages' array.

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 description is a single sentence of appropriate length, avoiding redundancy. However, it suffers from under-specification rather than true conciseness—every word earns its place, but there are too few words to adequately describe a 6-parameter tool.

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

Completeness1/5

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

Given the tool complexity (6 parameters with nested objects), game-specific domain terminology (events, pages), and complete absence of schema descriptions or output schema, the description is entirely inadequate. It fails to explain the domain model, parameter relationships, or return behavior.

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

Parameters1/5

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

Schema description coverage is 0%, requiring the description to compensate by explaining parameter semantics. The description mentions no parameters at all, leaving critical parameters like 'pages' (array type with unknown structure), 'note', and coordinate system (x/y) completely undocumented.

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 states a clear verb ('Create') and resource ('event on a map'), providing basic purpose identification. However, it fails to distinguish from sibling tools like 'create_map' (which creates the map itself) or clarify what constitutes an 'event' in this game development context, leaving ambiguity regarding the tool's specific scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives like 'update_map_event' (for existing events) or 'add_event_command', nor does it mention prerequisites such as requiring an existing mapId.

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