Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

update_starting_position

Set the initial player spawn location in RPG Maker MZ/MV by specifying map coordinates. This tool configures where the game begins when started.

Instructions

Update the game starting position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYes
xYes
yYes

Implementation Reference

  • The handler function that updates the starting position in System.json.
    export async function updateStartingPosition(
      projectPath: string,
      mapId: number,
      x: number,
      y: number
    ): Promise<void> {
      const system = await getSystem(projectPath);
      system.startMapId = mapId;
      system.startX = x;
      system.startY = y;
    
      const systemPath = getDataPath(projectPath, 'System.json');
      await writeJsonFile(systemPath, system);
    }
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 but fails to deliver. While 'Update' implies mutation, the description does not clarify if this change is persistent, if it affects active game sessions, requires specific permissions, or what happens to the previous starting position. It provides minimal behavioral context beyond the operation type.

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?

While brief at only four words, this represents under-specification rather than appropriate conciseness. The single sentence does not earn its place by providing actionable guidance, leaving the agent with insufficient information to invoke the tool correctly.

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?

For a tool with three undocumented parameters, no annotations, and no output schema, the three-word description is completely inadequate. It lacks explanation of the coordinate system, map reference semantics, return values, or side effects—essential information given the complete absence of structured metadata.

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?

The input schema has 0% description coverage for its three parameters (mapId, x, y), and the description completely fails to compensate for this gap. It does not explain that x and y represent coordinates, what coordinate system is used, or that mapId refers to a specific game map. The agent is given no semantic information to correctly populate these required fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update the game starting position' essentially restates the tool name with spaces added, constituting a tautology. While it identifies the verb (Update) and resource (game starting position), it fails to distinguish this tool from sibling update tools like update_actor or update_map_event, and does not clarify what 'starting position' means in the context of the game system.

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?

The description provides no guidance on when to use this tool versus alternatives such as update_actor or create_map. There are no prerequisites mentioned, no warnings about side effects, and no indication of when this update is appropriate versus other state modifications.

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