Skip to main content
Glama
shapez 1 游玩 MCP

shapez 1 游玩 MCP

by aymidasing

entities

Read-only

Inspect grouped or frozen building details across half-open map regions, filter by kind, and paginate results.

Instructions

查询建筑分组或冻结明细。region 为半开 tile 区间,摘要的 firstCursor 用于同一视图的分页。

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two genuinely non-obvious behaviors: that region is a half-open tile interval and that pagination must stay on the same view, but it says nothing about page limits or what a summary contains beyond firstCursor.

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 stated first and the two non-obvious constraints following; no filler. It is arguably too compressed for a schema with four oneOf variants, 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?

An output schema exists, so return values need not be described, and region/cursor semantics are nicely covered. However, the mode variants (summary vs region vs page) and the kind filter are left entirely to the schema, which is thin for a multi-variant tool.

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?

Schema coverage is 100%, so the baseline is 3, yet the description goes beyond the schema by explaining that region bounds are half-open — a semantic the JSON schema cannot express — and by tying the cursor token to the summary's firstCursor rather than to an arbitrary opaque value.

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 concrete operation — querying building groupings ('建筑分组') or frozen detail records ('冻结明细') — which tells an agent the resource is entity/building data rather than belts or map tiles. It does not contrast itself with siblings such as map_region or preview_belts, so the boundary stays implicit.

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 mention of a summary's firstCursor for paging within the same view hints at the summary→page workflow, but no explicit when-to-use or when-not-to-use guidance is given for the region, page, or kind variants. An agent must infer mode selection from the schema's oneOf rather than from prose.

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