Skip to main content
Glama
shapez 1 游玩 MCP

shapez 1 游玩 MCP

by aymidasing

status

Read-only

Retrieve the current save, level, world scale, viewport, and available capabilities in shapez 1 for agent inspection.

Instructions

查看当前活动存档、关卡、世界规模、视野和可用能力。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 the safety profile is covered and the description adds the informational scope of the response. It does not say whether the snapshot is live or cached, or whether it changes as the game progresses. With annotations and an output schema carrying much of the burden, a 3 is appropriate.

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 that enumerates the returned state without filler. It is appropriately sized for a no-argument status call, though the flat list of nouns could be grouped for faster scanning.

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 zero parameters, an output schema, and read-only annotations, the description covers what an agent needs to decide to call it. The only real gap is the lack of differentiation from operation_status, which matters given the ambiguous name 'status'.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed by framing the call as a pure read of current state.

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 opens with a specific verb (查看) and enumerates the resources returned: active save, level, world size, viewport, and available capabilities. That makes the tool's purpose unambiguous. It does not, however, distinguish itself from the sibling operation_status, which an agent could easily confuse with a generic 'status' call.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named despite operation_status sitting in the sibling list. The usage is only implied by the word 'current' in the enumeration, leaving the agent to guess whether this is a snapshot of game state or an operation-tracking endpoint.

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