Skip to main content
Glama

layout_status

Retrieve a complete status overview of your model railroad layout: connectivity, DCC power, active locomotives, block occupancy, and sensor states, with independent error handling for each section.

Instructions

One-call overview of the whole layout: connectivity, power, active locomotives, blocks, sensors.

Call for "what's happening on the layout?"/"is everything ready?"/"donne-moi l'état du layout" — a broad status question with no single named target. Never chain list_systems + list_roster + list_blocks + list_sensors yourself, this gathers them in one call.

Different from system_status (reachability + DCC power only): this adds every locomotive THIS session holds a throttle for (with speed/direction), block occupancy, and sensor states — fuller, at the cost of more JMRI calls. Use system_status when only reachability/power is in question.

No side effects. Each section is fetched independently with its own "error" key on failure — one section failing doesn't block the rest.

Returns {"reachable", "version", "systems": [...], "locomotives": [], "blocks": [...], "sensors": [...]}, with "*_error" keys for any failed section.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It discloses no side effects, independent fetching per section, and error key handling on failure. Full transparency.

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?

Well-structured and concise; each sentence provides essential information without redundancy. Front-loaded with purpose, then usage, then behavior, then output.

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?

Given no output schema, description sufficiently explains return structure and error handling. Covers all relevant aspects for effective use.

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?

No parameters exist, so baseline 4 applies. Description adds no parameter info but none is needed; schema coverage is 100% (trivially).

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?

Description clearly states it provides a 'one-call overview of the whole layout' listing specific components (connectivity, power, locomotives, blocks, sensors). Distinguishes from sibling system_status by scope.

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?

Explicitly says when to call ('what's happening on the layout?') and when not to call (use system_status for reachability/power only). Advises against chaining multiple calls.

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/HO44-PROJECT/MrJ-JMRI-MCP'

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