Skip to main content
Glama
ober37

AC Infinity MCP

break_out_of_automation

Break a port free from Advance Automation by disabling the governing automation and locking co-ports to their current speeds, allowing safe manual control on AC Infinity controllers.

Instructions

Break a port out of Advance Automation control and lock co-governed ports.

This is the safe way to manually override a port that is currently under Advance Automation. It:

  1. Checks that the port is actually under automation (idempotent: no-ops if not).

  2. Finds the governing automation.

  3. Identifies all other ports in the same automation as the target port (co-ports). Only those ports are locked — ports in other automations or empty ports are unaffected.

  4. On dry_run=False: a. Disables the automation. b. Locks each co-port to its current manual speed (prevents unexpected speed changes). c. Leaves the target port free for your manual change.

Defaults to dry_run=True. For live execution (dry_run=False), you must supply confirm_automation_name matching the automation name (case-insensitive) as a safety confirmation.

Args: device_id: The AC Infinity device code (from discover_devices). port: The port number you want to break free (1-based). dry_run: If True (default), returns the execution plan without making changes. confirm_automation_name: Required when dry_run=False — the name of the automation to disable, for safety confirmation.

Returns: Dry-run: JSON plan with sequence of steps, co_ports_to_lock, estimated_duration. Live: JSON with co_ports_locked and target_port_freed. Idempotent: {"info": "Port is not currently under automation control."} On failure returns {"error": "..."}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
portYes
dry_runNo
confirm_automation_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: idempotent, locks co-ports, requires safety confirmation, dry_run versus live, and return formats. It is transparent about every step and outcome.

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 well-structured with bullet points and sections, but it is somewhat verbose. However, it is front-loaded with the purpose and process, and every sentence adds value.

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?

The description is complete: it covers idempotent, dry_run, live, error responses, and safety confirmation. Given the output schema exists, the return values are adequately explained.

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?

Despite 0% schema description coverage, the description explains each parameter in detail (device_id from discover_devices, port 1-based, dry_run default, confirm_automation_name required for live), adding significant meaning beyond the schema.

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: 'Break a port out of Advance Automation control and lock co-governed ports.' It uses a specific verb and resource, and the step-by-step process differentiates it from sibling tools like disable_advance_automation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool ('safe way to manually override a port') and mentions idempotent behavior and dry_run default. It lacks explicit when-not-to-use or alternatives, but the context is clear.

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/ober37/ac-infinity-mcp'

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