Skip to main content
Glama

secure_layout

Ends a model railroad session by stopping all locomotives, turning off all layout lights, and releasing throttles to secure the layout.

Instructions

Put the whole layout into a known safe resting state — the end-of-session "I'm done for today" command.

Args: release_throttles: True (default) to also release every locomotive's throttle at the end. False to stop/light-off every locomotive but keep throttles acquired.

Call for "I'm done for today, secure the layout"/"sécurise le layout"/"on arrête pour aujourd'hui" — a broad end-of-session request naming the layout as a whole, not one locomotive. Never chain stop/set_loco_lights/set_layout_lights/release_throttle yourself, this runs the full sequence server-side in one call.

Runs in order: 1) every acquired locomotive smoothly stopped (ramped, not abrupt), faced forward, lights off — same as park_locomotive, independently per locomotive; 2) every layout light (JMRI Light objects) turned off — same as set_layout_lights(False); 3) if release_throttles is True (default), every throttle released.

NOT power_off_all (cuts DCC track power itself, unconditionally, including locomotives never acquired here — more drastic, never touches power) and NOT emergency_stop_all (motion-only, no lights/release). Only reaches locomotives THIS session has acquired.

Returns {"locomotives": [<per-locomotive stop/lights/release result>...], "layout_lights": }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
release_throttlesNo
Behavior5/5

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

With no annotations, the description fully discloses behavior: the sequence of steps (ramped stop, lights off, throttle release), parameter effect, return format, and what it does NOT do.

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?

Well-structured with sections (Args, sequence), but slightly lengthy. Every sentence adds value, but could be tightened without losing clarity.

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 the complexity (multi-step, parameter, sibling comparisons) and no output schema, the description is complete: covers purpose, usage, behavior, parameter, and return structure.

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

Parameters5/5

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

Schema coverage is 0%, but the description explains the release_throttles parameter in detail, including default and effect, fully compensating for the missing schema descriptions.

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's purpose: 'Put the whole layout into a known safe resting state — the end-of-session command.' It uses specific verbs and resources and explicitly distinguishes from siblings like power_off_all and emergency_stop_all.

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?

Provides explicit when-to-use ('Call for I'm done for today, secure the layout') and when-not-to ('Never chain stop/set_loco_lights/set_layout_lights/release_throttle yourself'), and contrasts with 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/HO44-PROJECT/MrJ-JMRI-MCP'

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