Skip to main content
Glama

Set spawn point

set_spawnpoint
Idempotent

Set an online Minecraft player's respawn point to specific X, Y, Z coordinates or to their current position.

Instructions

Set where an online player respawns: the given position, or where they stand now.

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": {
      "username": "<username>"
    },
    "name": "set_spawnpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoBlock X; give x, y and z together or leave all out.
yNoBlock Y; give x, y and z together or leave all out.
zNoBlock Z; give x, y and z together or leave all out.
usernameYesExact, case-sensitive name of an online player.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the meaningful behavioral fact that omitting coordinates captures the player's current standing position, but it omits persistence ('does this survive a restart?') and the online-player precondition's consequences.

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?

A single sentence with zero filler, front-loading the resource being mutated and then the two positional modes. Nothing is redundant with the title and nothing could be cut without losing information.

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?

With an output schema present and full annotation coverage, the description needn't explain return values or safety. It is still thin for a mutation tool: it does not mention whether the player must be online at call time or what occurs if the username does not match a live player, which are the main failure modes an agent would hit.

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, but the description contributes genuine extra meaning: the schema only says to supply x, y, z together or leave them out, while the description explains that leaving them out means 'where they stand now'. That resolves the ambiguity of the null-default behavior rather than restating the schema.

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 gives a specific verb and resource ('Set where an online player respawns'), which is concrete enough that an agent can distinguish this per-player spawn tool from world-level siblings like set_world_spawn. It stops short of naming any sibling explicitly, so it lands just below the top mark.

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 phrase 'the given position, or where they stand now' implies the two usage modes (explicit coordinates vs. snapshot current location), which is useful guidance. However, it never states when to prefer this over set_world_spawn or what happens if the named player is offline, leaving the main routing decision to inference.

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