Skip to main content
Glama

acquire_throttle

Gain control of a locomotive by its DCC address and receive its current speed and direction.

Instructions

Acquire control of a locomotive by its DCC address, and report its current state.

Args: address: The locomotive's DCC address. prefix: Optional command station prefix (e.g. "O", "Z", "R") to target when more than one DCC system is connected. Omit to auto-detect from the roster's DccSystem attribute (see list_roster's "dcc_system" field), else JMRI's default station. Pass explicitly only to override auto-detection.

You usually do NOT need to call this explicitly before set_speed/ stop/emergency_stop — those auto-acquire on first use (same DccSystem auto-detection) for a smoother voice UX. Call this directly when you want a loco's current speed/direction before deciding what to do (the reply reports both), or to override the detected station via an explicit prefix.

Safe to call again on an address already acquired this session — JMRI just re-confirms it, no error or loco reset. Release with release_throttle when done, though not required: JMRI releases every throttle this session holds if the MCP server disconnects.

In exhibition mode with an address allowlist configured, an address outside it is refused here (and by every other throttle tool, routed through this same check) — see enter_exhibition_mode.

Returns "system": full name of the command station actually used, only when non-default — mention it to the user when present.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNo
addressYes
Behavior5/5

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

With no annotations, the description fully discloses idempotency, release on disconnect, exhibition mode rejection, and the return field 'system' — covering all important behavioral traits.

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 with purpose first, then args, usage, safety, and return note. Every sentence adds unique value without redundancy.

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 and only two parameters, the description covers acquisition purpose, return content, error conditions (exhibition mode), and integration with other tools—fully adequate for correct invocation.

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 schema has zero description coverage, but the description explains both parameters in detail: address is required, prefix is optional with clear guidance on auto-detection vs explicit override.

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 starts with a specific verb-object pair ('Acquire control of a locomotive by its DCC address') and clearly distinguishes from sibling tools like set_speed and stop by noting auto-acquire behavior.

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 states when to call directly (to get current state or override prefix) versus letting auto-acquire handle it, and mentions release and exhibition mode restrictions.

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