Skip to main content
Glama
shapez 1 游玩 MCP

shapez 1 游玩 MCP

by aymidasing

resources

Read-only

Query resource patches on the map and filter them by canonical keys such as color:green or shape:CuCuCuCu to locate specific deposits.

Instructions

查询资源斑块。用 color:green 或 shape:CuCuCuCu 等规范键筛选。

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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. The description adds nothing about pagination, the 1–64 limit, cursor continuation, or how summary versus region versus page results differ. With annotations doing part of the work, this is a middling score rather than a failure.

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?

Two short sentences with the resource named first and the filtering hint second; nothing is wasted. It is efficient, though efficiency here comes partly from omitting necessary detail.

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

Completeness2/5

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

The input schema is a four-branch oneOf (summary, region, page, page+cursor) with required-field differences and a 1–64 limit, yet the description mentions none of these modes. For a tool of this structural complexity, two sentences are not enough to call it correctly. The existing output schema offsets the need to describe return values, but not the mode selection gap.

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 coverage is reported at 100%, so structural documentation is not the description's burden. The one genuine contribution is the canonical key format ("color:green", "shape:CuCuCuCu"), which clarifies the otherwise opaque Key string and kind enum. The mode/region/cursor semantics remain unexplained, so it lands at the baseline.

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

Purpose3/5

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

"查询资源斑块" states a verb (query) and a resource (resource patches), plus a filtering example, so the basic operation is clear. However, "资源斑块" is domain jargon that is never grounded, and nothing distinguishes this from siblings such as entities or map_region. An agent can tell it reads something resource-related but not exactly what.

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 when-to-use guidance, no mention of alternatives, and no indication of which of the four schema modes to pick. The only implied usage is 'use it when you want to filter resource patches', which the agent must infer.

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