Skip to main content
Glama

Rooms and zones

rooms_and_zones

Inventory fortress rooms and zones: bedrooms, dining halls, hospitals, wells, temples, taverns, libraries, guildhalls, plus ghosts. Pair each supply with demand-side numbers to reveal shortages.

Instructions

The fort's facility inventory, each count paired with its demand-side number where one exists: bedrooms (assigned/unassigned vs. adults without one), dining halls and seats, the hospital (beds, traction benches, whether a well is inside, and medical supplies physically stocked), wells (working state and water source: water/frozen/magma/unknown), temples (dedicated deities, whether an all-inclusive temple exists, and deities worshipped by citizens that lack a dedicated temple), taverns, libraries, guildhalls, and coffins free vs. dead awaiting burial (loose corpses of the fort's own race). ghosts reports active apparitions currently on the map (active[], fog-of-war gated) plus unquiet_dead_count — this civ's dead who are world-flagged as unquiet ghosts (flags.ghost) and NOT represented in the visible active[] list. This is deliberately not the same as "confirmed absent locally": a ghost hidden behind fog of war is excluded from active[] (never leaked) but still counted here, since the world-level ghost fact is fair game even when its exact location isn't. The supply-side companion to unmet_needs(). Reports what the fort has, not what to build. Wells are capped (wells_truncated flags the overflow); bedroom and coffin detail is aggregated to counts. Returns {"error":"no fort loaded"} if no fort is active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Despite no annotations, the description discloses critical behavioral traits: well truncation flag, aggregation of bedroom/coffin counts, ghost visibility rules (fog-of-war gated active[] vs world-flagged unquiet count), and the error condition when no fort is loaded. This goes well beyond minimal requirements.

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 long but every sentence carries substantive information about data categories or edge cases. It could benefit from bullet points, but the single-paragraph structure is acceptable given the tool's complexity and the need to explain nuanced behavior.

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 annotations and no output schema, the description must carry the full burden, and it does. It covers all data categories, explains the ghost counting logic in depth, notes truncation, and specifies the error case. It is fully self-contained.

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?

The tool has zero parameters, so the baseline is 4. The description thoroughly explains what the output contains, which is the main semantic burden; no parameter descriptions are needed.

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 clearly states the tool reports the fort's facility inventory with specific categories (bedrooms, dining halls, hospital, wells, temples, etc.) and explicitly positions it as the supply-side companion to unmet_needs(), distinguishing it from that sibling. The scope is precise and detailed.

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?

The description explicitly names the companion tool unmet_needs() and clarifies that it 'Reports what the fort has, not what to build', providing clear when-to-use and what-not-to-use guidance. This directly helps an agent choose between alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexanderolvera/dfhack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server