Skip to main content
Glama
shapez 1 游玩 MCP

shapez 1 游玩 MCP

by aymidasing

map_region

Read-only

Retrieves a specified rectangular map region as rows or an image, with regular, wire, or both layers, to inspect or control Shapez gameplay.

Instructions

完整局部地图。region=[x0,y0,x1,y1] 右下不含,最多 32×32,format=rows/image,layer=regular/wires/both。

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": {
      "region": "<region>"
    },
    "name": "map_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNo
formatNo
regionYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds the 32×32 size cap, which implies a failure or clamp condition, but never says what happens when a region exceeds that cap, nor does it explain what the image format actually returns.

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 compact with the region format and size cap front-loaded and zero filler sentences. The telegraphic style is terse to the point of terseness becoming a minor risk, but nothing is wasted.

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

Completeness3/5

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

With an output schema present, return values need not be described, and the size/coordinate constraints are supplied. What remains missing is whether the coordinate system origin is fixed, and the behavioral consequence of an oversized region — gaps that matter for a 3-parameter mapping tool.

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 0%, so the bare integer fields x0/y0/x1/y1 carry no meaning on their own. The description compensates by defining the [x0,y0,x1,y1] ordering and the bottom-right-exclusive convention, which is genuine added value, but it merely echoes the format/layer enum values without explaining rows-vs-image or regular-vs-wires-vs-both.

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

Purpose4/5

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

The description's opening phrase ('完整局部地图') names a specific resource — a complete local map of a region — and combined with the region/format/layer keywords distinguishes it from siblings like screenshot, entities, and preview_belts. It lacks an explicit verb, so it is clear rather than exemplary.

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

Usage Guidelines3/5

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

The description states real usage constraints (max 32×32 region, bottom-right exclusive) but gives no when-to-use guidance and never mentions the sibling alternatives (screenshot, entities) that an agent could confuse it with. Usage is implied by the constraint set rather than by routing guidance.

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