Skip to main content
Glama

Force-load chunk

set_chunk_force_loaded
Idempotent

Keep or release the main-world chunk at block coordinates (x, z) so redstone and farms run without players nearby. Set force_loaded true to hold it; false releases it.

Instructions

Keep (or stop keeping) the chunk containing block (x, z) of the main world loaded, so redstone and farms there run without players nearby.

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>",
      "z": "<z>",
      "force_loaded": "<force_loaded>"
    },
    "name": "set_chunk_force_loaded"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesBlock X coordinate (east is +X).
zYesBlock Z coordinate (south is +Z).
force_loadedYesTrue keeps the chunk loaded without players; false releases it.

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 this is a non-readOnly, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds genuinely useful information beyond that: only the main world can be force-loaded, and the boolean both sets and releases the flag. It is silent on permission requirements and on any cap on the number of force-loaded chunks, which matters for a server-affecting mutation.

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 well-formed sentence with the action and its consequence front-loaded and zero filler. Nothing is redundant with the title or the schema.

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?

With a full input schema, an output schema, and annotations covering safety and idempotency, the description only needed to convey purpose and scope, which it does. The remaining gap is operational context such as force-load limits or server-performance impact, which would be nice but is not essential to invoking it correctly.

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%, including axis direction hints and the meaning of force_loaded, so the baseline is 3. The description adds only that the coordinates refer to the main world's block grid; it contributes no coordinate format or range detail 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 pair ('keep or stop keeping') and resource (the chunk containing block x,z), plus the observable effect ('redstone and farms run without players nearby'). It also constrains scope to the main world, which distinguishes it clearly from a generic block-setter. It does not explicitly name the read counterpart get_chunk_force_loaded, so it falls short of full sibling differentiation.

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?

Usage is implied by the stated effect: call it when you want farms/redstone to run without players. There is no explicit when-not guidance, no mention of querying current state with get_chunk_force_loaded first, and no note about server limits on how many chunks can be force-loaded.

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