Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

get_map

Retrieve RPG Maker MZ/MV map data by specifying a map ID to access game level information for development or analysis.

Instructions

Get map data by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapIdYesThe ID of the map to retrieve

Implementation Reference

  • The implementation of the get_map tool which reads map data from a JSON file.
    export async function getMap(projectPath: string, mapId: number): Promise<MapData> {
      const mapPath = getMapPath(projectPath, mapId);
      return await readJsonFile<MapData>(mapPath);
    }
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It states nothing about the read-only/idempotent nature, what the return structure contains (tile data? events?), or error handling behavior for non-existent IDs.

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?

Extremely brief at five words with no redundancy. While efficient, it may be overly terse given the lack of annotations and output schema, leaving significant interpretive burden on the agent.

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?

Lacks output schema documentation, which is critical for understanding what 'map data' includes (e.g., tilesets, events, dimensions). Given the complex sibling ecosystem (30+ tools), the description inadequately clarifies this tool's specific niche.

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

Parameters3/5

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

Schema coverage is 100% for the single parameter, so the structured definition already documents 'mapId' adequately. The description adds no additional semantic context (e.g., where to obtain valid IDs, format constraints), warranting the baseline score.

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 basic verb ('Get'), resource ('map data'), and lookup method ('by ID'), which is minimally sufficient. However, it fails to distinguish from siblings like `get_map_infos` (which likely returns metadata/lists) or clarify what constitutes 'map data' in this domain.

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?

Provides no guidance on when to use this versus `get_map_infos`, `get_map_events`, or `paint_map`. No mention of prerequisites (e.g., valid ID range) or error conditions (e.g., invalid 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