Skip to main content
Glama

park_locomotive

End a locomotive's session by ramping down speed, setting direction forward, turning off lights, and releasing the throttle in one call.

Instructions

Put ONE locomotive to rest for the session: smooth stop, forward, lights off, throttle released.

Args: address: The locomotive's DCC address.

Use for "éteins la loco"/"coupe les moteurs"/"put the 3 to bed"/ "park the autorail"/"shut down the autorail" — end-of-session shutdown for one locomotive, not a mid-run pause (use stop).

NOT stop/emergency_stop (speed only, throttle stays acquired, lights untouched) and NOT set_power (DCC station's own power, JMRI-wide). This tool only touches this one locomotive's session state (speed + lights + release), never system power.

Four steps, one call: (1) ramp down to 0, duration scaled to current speed (up to ~3s at full speed, shorter/none if already slow); (2) flip to forward if in reverse (safe, since speed is 0 by now); (3) turn off every light-related function, same as set_loco_lights(address, False); (4) release the throttle.

If never acquired, steps 1-2 are skipped, but step 3 still auto-acquires (like set_loco_lights always does) so step 4 always has something to release.

Never call set_speed/stop, set_direction, set_loco_lights, and release_throttle yourself in sequence for a shutdown request — use this tool.

Returns {"address", "stopped": bool, "direction": "forward", "lights": , "released": bool}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
Behavior5/5

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

With no annotations, the description carries full burden. It details the four steps, edge cases (never acquired, reverse direction, auto-acquire for lights), and what the tool does NOT affect (system power, other locomotives). No annotation contradiction.

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 lengthy but every sentence adds valuable detail. It is front-loaded with a summary. Could be slightly trimmed, but overall efficient for the complexity.

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 tool's complexity (multi-step, edge cases) and lack of output schema, the description covers everything needed: steps, edge cases, return value structure, and contrasts with alternatives. No gaps.

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?

The single parameter 'address' has no description in the input schema (0% coverage). The description adds full meaning: 'The locomotive's DCC address', which is clear and sufficient.

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 puts one locomotive to rest for the session, with specific actions (smooth stop, forward, lights off, throttle released). It distinguishes from siblings like 'stop', 'emergency_stop', and 'set_power' by explaining what those tools do differently.

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 specifies when to use (end-of-session shutdown for one locomotive) and when not to use (mid-run pause, use 'stop'). Provides alternative natural language commands and contrasts with 'stop', 'emergency_stop', and 'set_power'.

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