Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

update_map_event

Modify map event properties in RPG Maker MZ/MV projects to adjust character interactions, dialogue, or triggers within game maps.

Instructions

Update a map event's properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYes
eventIdYes
updatesYes

Implementation Reference

  • The actual implementation of the update_map_event tool handler.
    export async function updateMapEvent(
      projectPath: string,
      mapId: number,
      eventId: number,
      updates: Partial<MapEvent>
    ): Promise<MapEvent> {
      const map = await getMap(projectPath, mapId);
    
      if (!map.events[eventId]) {
        throw new Error(`Event ${eventId} not found on map ${mapId}`);
      }
    
      map.events[eventId] = { ...map.events[eventId]!, ...updates };
    
      const mapPath = getMapPath(projectPath, mapId);
      await writeJsonFile(mapPath, map);
    
      return map.events[eventId]!;
    }
  • src/index.ts:411-420 (registration)
    The registration of the update_map_event tool, including its schema.
    name: 'update_map_event',
    description: 'Update a map event\'s properties',
    inputSchema: {
      type: 'object',
      properties: {
        mapId: { type: 'number' },
        eventId: { type: 'number' },
        updates: { type: 'object' },
      },
      required: ['mapId', 'eventId', 'updates'],
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. 'Update' implies mutation but fails to specify if this is a partial update ( PATCH-like) or full replacement, whether omitted properties are preserved, or what the return value indicates.

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

Conciseness2/5

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

Extremely brief (5 words), but this represents under-specification rather than efficient communication. Given the complexity (nested object parameter, mutation behavior), the length is inadequate and front-loads no useful constraints.

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?

Completely inadequate for tool complexity. Mutation operation with no annotations, no output schema, undocumented parameters, and a flexible 'updates' object requires detailed explanation of valid update paths, which is entirely absent.

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 has 0% description coverage with 3 parameters including a nested 'updates' object. Description adds zero semantic value—fails to explain what valid properties exist within the updates object, what mapId/eventId reference, or expected data formats.

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?

States the verb (Update) and resource (map event's properties), providing basic clarity. However, it lacks specificity regarding which properties can be modified and does not differentiate from sibling tools like create_map_event or get_map_event.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., create_map_event for new events). No mention of prerequisites, idempotency, or side effects.

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