Skip to main content
Glama
shapez 1 游玩 MCP

shapez 1 游玩 MCP

by aymidasing

sample_flow

Read-only

Samples logistics and delivery progress in a specified region over a time window, returning a time series and incremental changes.

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": {
      "region": "<region>",
      "points": "<points>"
    },
    "name": "sample_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes
regionYes
samplesNo
secondsNo

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 useful behavior beyond that by stating that the tool samples multiple times over a time window and returns a sequence plus increments, but it does not disclose latency, blocking behavior, sampling limits, or rate characteristics.

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?

The description is a single front-loaded sentence with no filler, so it is concise and focused. It is arguably too terse for a four-parameter tool with complex region and point inputs, but it does not waste words.

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?

Given four parameters, 0% schema description coverage, and a required 'points' parameter that is not described, the definition is not complete enough to explain invocation semantics. The existing output schema and annotations reduce the need to explain return values and safety, but the missing parameter detail remains a significant gap.

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%, so the description must carry the burden of explaining four parameters. It mentions the specified region and temporal sampling in general terms, but it never explains the required 'points' parameter or maps 'samples' and 'seconds' to the described time window and repetition.

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 states a specific verb (sample), resource (logistics and delivery progress in a specified region), and a temporal pattern (multiple samples within a time window). It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as status or operation_status.

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?

Usage is implied: use this when repeated temporal sampling of logistics and delivery progress in an area is needed. However, there is no explicit when-to-use guidance, no when-not guidance, no prerequisites, and no named alternative.

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