rpgmaker-mz-mcp

Overview Schema Source Related Servers Discussions Admin

resize_map

Resize an RPG Maker MZ map to new width/height, repadding every tile-data layer. Existing tiles stay where grids overlap, new cells are blank, shrinking crops. Warns about events left outside the new bounds.

Instructions

Resize a map to new width/height, safely repadding every z-layer of its tile data (existing tiles kept where the old and new grids overlap; new cells blank; shrinking crops). This is the ONLY safe way to change a map's dimensions — update_map refuses a width/height change because it would not resize the tile array. Warns about any event left outside the new bounds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mapId": "<mapId>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "resize_map"
  }
}

Input Schema

Name	Required	Description
`mapId`	Yes	The ID of the map to resize
`width`	Yes	New width in tiles
`dryRun`	No	Preview only: return a diff of what would change without writing to disk.
`height`	Yes	New height in tiles
`verbose`	No	Echo the full written record instead of the default summary. Off by default: the response reports identity, counts and command-list shape, which is what you would assert on, and omits the parameters/conditions you would only re-read. Read the full record with the matching get_* tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.3.0Aug 3, 2026

addedInput schema / properties / verbose

Added value: +{
+  "description": "Echo the full written record instead of the default summary. Off by default: the response reports identity, counts and command-list shape, which is what you would assert on, and omits the parameters/conditions you would only re-read. Read the full record with the matching get_* tool.",
+  "type": "boolean"
+}

First observedv1.2.0Jul 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does so richly: repadding every z-layer, preserving tiles on overlap, blank new cells, cropping on shrink, and warning about events outside new bounds. It stops short of stating whether warned events are deleted or kept, and does not confirm the write-to-disk/commit behavior beyond the dryRun param.

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

Conciseness5/5

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

Three dense sentences, each earning its place: the core action with precise overlap/crop semantics, the critical alternative contrast, and the event-warning behavior. Dense and front-loaded with zero fluff.

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

Completeness4/5

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

With no output schema, the description compensates well by thoroughly covering behavioral complexity (z-layer repadding, overlap/crop semantics, the only-safe-route contrast, event warnings). It does not explicitly describe the response summary/record shape or confirm immediate persistence, but the verbose parameter in the schema partially covers return behavior.

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 description coverage is 100% — all 5 parameters (mapId, width, height, dryRun, verbose) have their own descriptions in the schema, so the baseline is 3. The description's "new width/height" adds little beyond the schema's "New width/height in tiles," and dryRun/verbose semantics are fully documented in the schema itself.

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

Purpose5/5

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

The description opens with a specific verb+resource combination: "Resize a map to new width/height, safely repadding every z-layer of its tile data." It also explicitly distinguishes from siblings: "This is the ONLY safe way to change a map's dimensions — update_map refuses a width/height change because it would not resize the tile array."

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: "This is the ONLY safe way to change a map's dimensions," and names the specific alternative (update_map) and why it is unsuitable for this purpose. The note about event warnings also clarifies a behavioral condition users should expect.

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

Deploy Server