Skip to main content
Glama

Chunks

list_chunks
Read-onlyIdempotent

Lists loaded chunks with entity and block entity counts, sorting by busiest to locate lag; inspect one chunk by coordinates for type breakdowns, player time, slime chunk, and force-load status.

Instructions

Loaded chunks with entity and block entity counts. sort entities or tileEntities puts the busiest first, which is where lag usually sits; counts by entity type are get_entity_summary. With chunk, that one chunk in detail: entities and block entities by type, how long players spent there, slime chunk, force-loaded. A chunk is 16×16 blocks; chunk X is block X divided by 16, rounded down.

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

Input Schema

NameRequiredDescriptionDefault
sortNo`coords` by default
chunkNoOne chunk, by chunk coordinates
limitNoHow many items to return; 0 answers only the total, to count without listing
worldNoWorld name, such as `world`, `world_nether`, `world_the_end`, or a key like `minecraft:the_nether`world
cursorNo`nextCursor` from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 establish the safe, read-only, idempotent profile. The description adds meaningful behavioral context beyond that: only loaded chunks are listed, sorting by entity type puts busiest chunks first, and chunk mode returns per-type counts, play time, slime chunk status, and force-loaded status. It stops short of explaining pagination or full 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose, then adds sort behavior, chunk-detail contents, and coordinate conversion. Every sentence carries useful information and none reads as padding.

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 no output schema, the description usefully explains what list mode and chunk-detail mode return. It leaves pagination behavior, limit semantics, and the world default to the schema, which covers them, so the description is nearly complete for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all five parameters. The description adds real meaning for `sort` (what `entities` and `tileEntities` actually do) and `chunk` (what the detail mode returns), plus coordinate conversion, but does not add prose meaning for `limit`, `world`, or `cursor`.

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 verb and resource: loaded chunks with entity and block entity counts. It also clearly distinguishes the chunk-detail mode and explicitly routes entity-type counts to the sibling get_entity_summary, so an agent can select it without opening the schema.

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?

It gives clear usage context: use `sort` set to `entities` or `tileEntities` to surface likely lag hotspots, and use `chunk` for one-chunk detail. It names get_entity_summary as the alternative for counts by entity type, though it does not explicitly state when not to use this tool.

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