Skip to main content
Glama
shapez 1 游玩 MCP

shapez 1 游玩 MCP

by aymidasing

restore_snapshot

Restore a construction site to its pre-build state by snapshot ID and the original request key, undoing applied changes accurately.

Instructions

按快照编号与原施工请求键恢复施工前现场。

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": {
      "snapshot": "<snapshot>",
      "applyRequestId": "<applyRequestId>",
      "requestId": "<requestId>"
    },
    "name": "restore_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
snapshotYes
requestIdYes
applyRequestIdYes

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 declare readOnlyHint=false and openWorldHint=false, and the restore verb is consistent with a mutation, so there is no contradiction. The description usefully adds that the operation is keyed to the original apply request, implying a targeted undo of a specific prior write. It does not disclose whether the restore is idempotent, what happens to state created after the apply, whether it is reversible, or what failures look like — notable gaps for a mutation tool.

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 front-loaded sentence with no filler; the operation and its two identifying inputs come first. It is efficient, though the terseness borders on under-specification for a mutation tool rather than excess verbosity.

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 explained, and the three required parameters are at least partly addressed. However, for a non-read-only restore with no destructiveHint and no description of scope of effect, an agent lacks enough to predict consequences or recover from a failed restore.

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 description carries the burden; it clarifies two of three parameters, explaining that 'snapshot' is a snapshot number and 'applyRequestId' is the key of the original apply request — a relational meaning the pattern constraint cannot convey. The third parameter, 'requestId', is left entirely undefined in both schema and description, so compensation is only partial.

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?

States a specific verb and resource: restore (恢复) the pre-construction site (施工前现场), parameterized by snapshot number and the original apply request key. An agent can tell this is a rollback-style mutation rather than a read, which separates it from siblings like status or preview_belts. It does not, however, name or contrast any sibling explicitly.

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 phrase 'original construction request key' (原施工请求键) implicitly signals the prerequisite that a prior apply operation must have occurred, so usage context is inferable. There is no explicit when-to-use/when-not guidance, no mention of preview_belts or apply_belts as the paired operation, and no stated error path if the apply request is unknown.

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