Skip to main content
Glama

Check chunk force-loading

get_chunk_force_loaded
Read-onlyIdempotent

Check whether the chunk containing a given block coordinate (x, z) in the main world is force-loaded, so you can verify persistent chunk loading before relying on it.

Instructions

Whether the chunk containing block (x, z) of the main world is force-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": {
      "x": "<x>",
      "z": "<z>"
    },
    "name": "get_chunk_force_loaded"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesBlock X coordinate (east is +X).
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful scope detail that queries target the main world and are addressed by block coordinate rather than chunk coordinate, but says nothing about edge behavior at unloaded areas or coordinate clamping.

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?

One sentence with zero filler and the scope ('main world') front-loaded. It is a grammatical fragment rather than a full sentence, but nothing is wasted.

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 an output schema present, return-value explanation is unnecessary, annotations cover the safety profile, and both parameters are fully documented. For a two-parameter boolean query, the description supplies what an agent needs, aside from the missing when-to-use routing.

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 the schema already documents both x (east +X) and z (south +Z) with bounds. The description adds only the mapping from block coordinates to a chunk, which is mildly useful but not beyond what a competent agent would assume.

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 precise predicate: whether the chunk containing block (x, z) of the main world is force-loaded. The verb+resource pairing is clear and the 'get_...' versus 'set_chunk_force_loaded' naming makes the read-only counterpart evident, though the description itself does not name the sibling.

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 explicit guidance on when to call this versus set_chunk_force_loaded, nor any prerequisites or exclusions. Usage is only implied by the question-form phrasing, leaving the agent to infer it is a state check.

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