Skip to main content
Glama

power_on_all

Restore power to every DCC system at once after a layout-wide power cut. Use this for generic 'turn everything on' requests without naming individual systems.

Instructions

Restore power to EVERY DCC system at once.

No arguments. Call this for phrases like "turn everything on", "power everything on", "allume tout", "remets le courant" — any request to restore/turn on power generically, without a specific system named. The inverse of power_off_all — use this after a layout-wide power cut (power_off_all, or manually turning systems off) to bring every system back to ON in one call, rather than naming each system individually with set_power.

IMPORTANT: restoring power does NOT make locomotives resume their previous speed. Every decoder stays stopped until a new speed command is sent — this only restores track power, it is not an "undo" of power_off_all or emergency_stop_all. Tell the user locomotives will need to be started again after calling this.

Each system's result is re-read and confirmed like set_power — check "confirmed" per system (see set_power's docstring for the "outdated_jmri_version" upgrade note, also per system here).

In exhibition mode this is REFUSED entirely (returns an error, no system is touched) — power_off_all is unaffected. See enter_exhibition_mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations, so description fully handles transparency. Discloses that power restoration does not resume locomotive speeds, that each system result is confirmed, and that exhibition mode refuses the action.

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 and informative, but slightly verbose with tangential notes (e.g., outdated_jmri_version). Still efficient overall.

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 or annotations, description covers all relevant aspects: behavior, side effects, edge cases, and interactions with sibling tools.

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?

No parameters, and description explicitly notes 'No arguments.' Schema coverage is 100%, so nothing more 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?

Clearly states it restores power to all DCC systems at once. Differentiates from sibling tools like set_power and power_off_all by specifying it is a global operation.

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 provides when to use (e.g., after a layout-wide power cut) and when not to (exhibition mode). Contrasts with alternatives like set_power for individual systems.

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