Skip to main content
Glama

park_all_locomotives

Stop every acquired locomotive with a smooth ramp-down, turn lights off, face forward, and release throttles in one call.

Instructions

Put EVERY currently-acquired locomotive to rest at once: smooth stop, forward, lights off, released.

Call for "éteins toutes les locos"/"coupe tous les moteurs"/"shut down every locomotive"/"put everything to bed" — the bulk counterpart to park_locomotive. Never loop park_locomotive yourself — this loops server-side in one call, running the same four-step sequence (proportional rampdown, face forward, lights off, release) independently per locomotive.

NOT emergency_stop_all (motion-only, no lights/release) and NOT system power off (cuts every locomotive on a DCC system regardless of driver — no single "power off everything" tool exists, see set_power per system). Only touches locomotives THIS session has a throttle for — one driven only from a JMRI panel or another session is untouched; nothing acquired yet returns {"locomotives": []}, not an error.

For ONE named locomotive use park_locomotive. For motion-only with no lights/release, use emergency_stop_all.

Returns {"locomotives": []} — each stopped independently, one failure doesn't block the others.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations exist, so description fully covers behavior: four-step sequence, server-side looping, independence per locomotive, scope limited to session's throttles, empty response for no acquisitions, non-blocking failures. No contradictions.

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, front-loaded with main action, followed by contrasts and details. Every sentence serves a purpose (clarifying scope, alternatives, behavior). No wasted words.

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?

Despite no output schema, description explains return format and error handling. Covers all relevant aspects: scope, sequence, comparisons, edge cases. Highly complete for a tool of this complexity.

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 schema coverage is 100%. The description adds context about the tool's action and behavior beyond the schema, earning a baseline 4.

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 every currently-acquired locomotive to rest with a specific sequence. It distinguishes itself from park_locomotive (single loco) and emergency_stop_all (motion-only), making the purpose unambiguous.

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?

Explicit guidance is given: use park_locomotive for one named loco, emergency_stop_all for motion-only. Warns against looping park_locomotive, stating this tool loops server-side. Clear when to use and not use.

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