Skip to main content
Glama
shapez 1 游玩 MCP

shapez 1 游玩 MCP

by aymidasing

preview_belts

Read-only

Simulate straight-belt placement or replacement to see per-tile before/after states and neighbor effects without changing the map; the plan stays valid for 60 seconds.

Instructions

预演直带施工:返回每格前后状态与邻格影响,不改变现场,计划 60 秒有效。

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>",
      "ops": "<ops>"
    },
    "name": "preview_belts"
  }
}

Input Schema

NameRequiredDescriptionDefault
opsYes
regionYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that while adding two traits annotations cannot express: the per-cell before/after plus neighbor-influence return shape, and a 60-second validity window on the produced plan. It doesn't say whether the plan is returned as an opaque handle to be consumed by apply_belts or how it expires, which keeps this below 5.

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?

A single dense sentence that front-loads the verb and then layers return shape, safety guarantee, and time limit in that order — no filler. It is packed tightly enough that the 60-second clause reads as an afterthought rather than a constraint on downstream use.

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?

An output schema exists, so return values need not be spelled out, and the read-only nature is covered by annotations. However, for a dry-run tool whose whole point is producing a plan consumed elsewhere, the definition omits how the plan is handed off and what region/ops actually mean, leaving real gaps for a 2-parameter simulation tool with 0% schema coverage.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters, so the description carries the full burden — yet it never mentions 'region' or the 'ops' array (1-8 place_straight/replace_straight entries with tile and direction). The phrase about per-cell before/after state hints that ops target cells, but the agent gets no explanation of region syntax, the 8-op cap, or why both tile forms are accepted.

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 names a specific verb and resource ('预演直带施工' — preview straight-belt construction) and immediately scopes it as non-mutating ('不改变现场'), which operationally separates it from the mutation sibling apply_belts. It stops short of naming that sibling explicitly, so the agent must infer the pairing from behavior rather than from a direct reference.

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?

'不改变现场' plus '计划 60 秒有效' gives clear usage context: this is a dry-run whose output is a short-lived plan, implying it should precede an actual apply. What's missing is an explicit statement of the alternative ('call apply_belts with the returned plan within 60s') and any precondition for calling it.

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