Skip to main content
Glama

Set world spawn

set_world_spawn
Idempotent

Sets the main world’s spawn point, defining where new players appear and compasses point.

Instructions

Set the main world's spawn point (where new players appear and compasses point).

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": {
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "set_world_spawn"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesBlock X coordinate (east is +X).
yYesBlock Y coordinate (height; the overworld build range is -64 to 319).
zYesBlock Z coordinate (south is +Z).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, idempotent, non-destructive, non-open-world mutation. The description adds genuine context by explaining the consequence of the change — new player appearance and compass direction — but says nothing about permissions, whether existing spawn points are overwritten, or whether coordinates are validated/snapped to safe ground.

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 front-loaded sentence with an embedded clarification; no padding, no restatement of the title.

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?

For a three-parameter mutation with full schema coverage and an output schema, the description covers purpose and effect adequately. The only gap is the absence of any routing hint relative to similar spawn-point tools.

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%, with x/y/z ranges and axis orientation documented in the schema itself. The description adds no coordinate semantics beyond what the schema provides, so the baseline 3 applies.

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 and resource — "Set the main world's spawn point" — and the qualifier "main world's" scopes it apart from per-player spawn tools. It does not name an alternative directly, so differentiation is implied by scope rather than explicit.

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 prerequisites, and no mention of when not to use it (e.g., versus a per-player spawn tool like set_spawnpoint). The parenthetical explains what the spawn point affects but not when an agent should reach for this tool.

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