Skip to main content
Glama
Sign In
rpgmaker-mz-mcp

rpgmaker-mz-mcp

by Redseb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_map_tile

Set a raw tile ID at specified X, Y coordinates on a map layer (0-5). Directly modify map data without autotile or passability checks.

Instructions

Set a single raw tile ID at (x, y) on a given z-layer (0-5). Note: tile IDs are raw engine integers; this is a low-level primitive without autotile/passability awareness.

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>",
      "x": "<x>",
      "y": "<y>",
      "layer": "<layer>",
      "tileId": "<tileId>"
    },
    "name": "set_map_tile"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX tile position
yYesY tile position
layerYesZ-layer 0-5 (0-1 lower, 2-3 upper, 4 shadow, 5 region)
mapIdYesThe ID of the map
dryRunNoPreview only: return a diff of what would change without writing to disk.
tileIdYesRaw tile ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It honestly notes raw engine integers and the lack of autotile/passability awareness, which is useful. But it does not disclose side effects like overwriting existing tiles, error behavior, or the difference between dryRun and actual writes, leaving some gaps.

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?

Two sentences, no fluff. The verb, target, coordinates, and layer bound are in the first sentence; the critical caveat about raw IDs and low-level behavior is in the second. Every word earns its place.

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?

For a simple setter with full schema coverage, the description covers the core semantics and key caveat. It doesn't explain return values or error conditions, but none are promised by the schema or output. Given the tool's low complexity, the description is nearly complete, only missing explicit alternative references.

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%, so the baseline is 3. The description reinforces key semantics (raw tile ID, layer range 0-5) but does not add significant detail beyond what the schema already provides. The dryRun property is only explained in the schema, not the description.

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 clearly states the action ('Set a single raw tile ID'), the resource (tile at x,y on a z-layer), and the scope (single, raw, 0-5). It distinguishes itself from bulk or high-level tools by explicitly calling itself a low-level primitive, separating it from siblings like paint_tiles and fill_area.

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

Usage Guidelines4/5

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

The context is clear: this is for setting a single raw tile without autotile/passability awareness, which implies it's not for bulk painting or high-level editing. However, it does not explicitly name alternative tools or state when not to use it, so it doesn't fully meet the bar for explicit exclusions.

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

Deploy Server

Other Tools