Skip to main content
Glama

Worlds

get_world
Read-onlyIdempotent

Retrieve Minecraft world details such as time, weather, difficulty, PvP, spawn, border, game rules, and load, or list all loaded worlds when no world is specified.

Instructions

One world: time of day (dayTime 0–23999: 0 sunrise, 6000 noon, 13000 night, 18000 midnight), day number, moon phase, ticks until night, whether beds work, weather, difficulty, PvP, the world's own spawn, the world border, game rule values, and load; server-wide TPS and players are get_server_status. Without world, every loaded world with its dimension key and player count. include adds rules (each game rule's type and default), size (chunks ever generated, explored area in km², size on disk), and respawn (the server's spawn point, where players join and respawn without a bed: world, x, y, z, yaw, pitch, respawnRadius, spawnProtection).

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": "get_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
worldNoWorld name or key, such as `world` or `minecraft:the_nether`; leave out to list every world
includeNoParts to add, such as ["rules"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare the operation as read-only, idempotent, non-destructive, and not open-world. The description adds meaningful behavioral context about default listing behavior, optional expansions, and the specific fields returned without an output schema.

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 front-loaded and every part is relevant, with no filler. However, the first sentence is a long, dense fragment listing many return fields, which makes it less readable than a more structured breakdown would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so thoroughly by describing both the default world fields and the optional include expansions. Annotations cover safety characteristics, so the remaining gaps are minimal.

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?

Although schema coverage is 100%, the description goes beyond the schema by explaining that omitting `world` lists all worlds and by detailing what each `include` value adds. In particular, it clarifies the contents of `rules`, `size`, and `respawn`, which are not fully conveyed by enum labels alone.

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 states a specific resource and the exact world state returned, including time, weather, difficulty, spawn, border, rules, and load. It also distinguishes the tool from get_server_status for server-wide TPS and players, so an agent can identify its role immediately.

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

Usage Guidelines5/5

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

It explicitly says omitting `world` lists every loaded world, and it routes server-wide metrics to get_server_status. The `include` guidance also clarifies how to expand the response for rules, size, and respawn details.

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