Skip to main content
Glama

Change a world

set_world

Adjust a Minecraft world's time, weather, difficulty, PvP, game rules, border, and spawn or respawn point in one call; only the settings you provide change.

Instructions

Change any of these at once; only what you give changes. The time of day (dayTime 0–23999: 0 sunrise, 1000 morning, 6000 noon, 13000 night, 18000 midnight), or move the clock forward with addTicks (24000 is a day). The weather (clear, rain, thunder), optionally for durationTicks (20 per second). The difficulty and PvP. rules sets game rules, such as { "keep_inventory": true, "players_sleeping_percentage": 50 } (get_world with include rules lists them). border resizes (optionally over transitionSeconds), moves, or changes the world border's damage and warnings. spawn is this world's own point, used by teleports to it; respawn moves the server's spawn point, where players join and respawn without a bed, into this world.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
pvpNoWhether players can hurt each other
rulesNoGame rule name to value
spawnNoThis world's own point
worldNoWorld name, such as `world`, `world_nether`, `world_the_end`, or a key like `minecraft:the_nether`world
borderNoOnly the fields given change
dayTimeNoTicks; 6000 noon, 18000 midnight
respawnNoThe server's spawn point; give x, y, z together, or none to use this world's own point
weatherNoNew weather
addTicksNoMoves the clock forward; 24000 ticks are one day
difficultyNoNew difficulty
durationTicksNoHow long the new weather lasts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv4.2.1
    • addedInput schema / properties / border / description
      Added value: +"Only the fields given change"
    • addedInput schema / properties / border / properties / damageAmount / description
      Added value: +"Per block past the buffer"
    • addedInput schema / properties / border / properties / damageBuffer / description
      Added value: +"Blocks past the border before damage"
    • addedInput schema / properties / border / properties / transitionSeconds / description
      Added value: +"Resize gradually; 0 at once"
    • addedInput schema / properties / border / properties / warningDistance / description
      Added value: +"In blocks"
    • addedInput schema / properties / dayTime / description
      Added value: +"Ticks; 6000 noon, 18000 midnight"
    • addedInput schema / properties / difficulty / description
      Added value: +"New difficulty"
    • addedInput schema / properties / rules / description
      Added value: +"Game rule name to value"
    • addedInput schema / properties / weather / description
      Added value: +"New weather"
  2. First observedv4.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-readonly, non-destructive, non-idempotent mutation, so the description doesn't need to restate safety. It adds real behavior the annotations don't carry: merge semantics ('only what you give changes'), relative vs absolute clock changes (addTicks vs dayTime), and the spawn vs respawn distinction. It omits any mention of permissions, reversibility, or response shape.

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?

Front-loaded with the merge-semantics rule, then grouped by concern (time, weather, difficulty, rules, border, spawn/respawn). It is one dense block of prose and the `world` parameter is never mentioned, but nothing is padded.

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?

Eleven mostly optional params across nested objects are grouped and explained, including the two easily-confused spawn params. Without an output schema the description gives no signal about what a successful change returns, which is the main residual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even at 100% schema coverage this adds meaning well beyond the schema: concrete dayTime landmark values (1000 morning, 13000 night), the ticks-per-day and ticks-per-second conversions, a worked `rules` example, and the critical clarification that `spawn` is this world's own point whereas `respawn` moves the server-wide spawn into this world — a distinction the schema alone does not make obvious.

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?

Opens with a specific verb+resource+scope: 'Change any of these at once; only what you give changes.' The read/write split from the sibling get_world is implicit but clear from 'change' plus the reference to get_world for listing rules.

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?

Establishes the partial-update usage model up front and points to get_world for discovering rule names, which routes the agent correctly for the read-before-write case. It stops short of explicit when-not-to-use guidance or noting that this is a non-idempotent mutation.

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