Skip to main content
Glama

Force-load a chunk

force_load_chunk
Idempotent

Keep a chunk loaded without nearby players so farms and redstone continue running, or release it to stop forcing that chunk.

Instructions

Keep a chunk loaded with nobody near, so farms and redstone keep running, or release it. list_chunks shows which are loaded.

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": {
      "chunkX": "<chunkX>",
      "chunkZ": "<chunkZ>",
      "forceLoaded": "<forceLoaded>"
    },
    "name": "force_load_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
worldNoWorld name, such as `world`, `world_nether`, `world_the_end`, or a key like `minecraft:the_nether`world
chunkXYesBlock X ÷ 16, rounded down
chunkZYesBlock Z ÷ 16, rounded down
forceLoadedYesfalse releases it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.2.1
    • addedInput schema / properties / chunkX / description
      Added value: +"Block X ÷ 16, rounded down"
    • addedInput schema / properties / chunkZ / description
      Added value: +"Block Z ÷ 16, rounded down"
    • addedInput schema / properties / forceLoaded / description
      Added value: +"false releases it"
  2. First observedv4.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, non-read-only, closed-world. The description adds real semantic context the annotations can't: the chunk stays loaded despite no players nearby, which is the observable behavioral effect. It doesn't mention persistence across restarts or any per-server limits, which would complete the picture.

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?

Two short sentences, front-loaded with the effect and ending with a discovery hint. No filler or redundancy.

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 four-parameter toggle with a fully documented schema and no output schema, the description covers what the tool does and the key operational effect. The remaining gap is durability/limits of force-loading, which an agent might want to know before relying on it.

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 coverage is 100% and documents all four parameters including defaults and the notable 'block X ÷ 16, rounded down' guidance. The description only implicitly echoes forceLoaded=false via 'or release it', adding essentially nothing beyond 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?

States a specific verb+resource (keep a chunk loaded / release it) and describes the mechanism ('with nobody near'). It is distinguishable from list_chunks, which it points to for inspection, though it doesn't explicitly contrast with other world-mutating siblings.

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?

Gives a clear reason to use it ('so farms and redstone keep running, or release it') and routes the agent to list_chunks to check current state. No explicit exclusions or limits (e.g., max force-loaded chunks), so it stops short of a 5.

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