Skip to main content
Glama

Spread players

spread_players

Teleports specified Minecraft players to random surface positions around a center point, enforcing minimum spacing and maximum range.

Instructions

Teleport players to random surface positions around a centre point (vanilla /spreadplayers).

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": {
      "usernames": "<usernames>",
      "center_x": "<center_x>",
      "center_z": "<center_z>",
      "spread_distance": "<spread_distance>",
      "max_range": "<max_range>"
    },
    "name": "spread_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
center_xYesX of the centre point.
center_zYesZ of the centre point.
max_rangeYesMaximum distance from the centre.
usernamesYesPlayers to spread out.
spread_distanceYesMinimum distance between players.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare that this is not read-only, not idempotent, and not destructive; the description adds useful behavioral context by specifying random surface positions and the vanilla command equivalent, consistent with non-idempotence. However, it does not explain online-player requirements, surface safety, failure behavior, or what happens if players cannot be placed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence that states the action, outcome, and vanilla equivalent without unnecessary wording.

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 full schema coverage, annotations, and an output schema, the description supplies enough core semantics for correct invocation: teleport players randomly to surface positions around a centre. It is only missing edge-case guidance about online-player validation and terrain safety.

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 100%, so the schema already carries the detailed parameter meanings. The description only implies that the coordinates define a centre point and does not add syntax or behavioral nuance beyond the schema for spread_distance, max_range, or usernames.

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

Purpose5/5

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

The description uses the specific verb 'Teleport' with the resource 'players' and qualifies the outcome as 'random surface positions around a centre point'. This is specific enough to distinguish the tool from read-only siblings like get_players and get_player_position.

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

Usage Guidelines4/5

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

The reference to 'vanilla /spreadplayers' gives clear context for agents or users familiar with the Minecraft command. It does not state exclusions or name alternatives, but the intended use case is clear from the operation described.

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