Skip to main content
Glama
ober37

AC Infinity MCP

disable_advance_automation

Disable an active Advance Automation on AC Infinity devices. Preview with dry_run or set dry_run=false to execute, turning governed ports off.

Instructions

Disable a currently enabled Advance Automation.

Reads current state before toggling — no-ops if already disabled. Defaults to dry_run=True — set dry_run=False to execute.

Live-tested (2026-05-22): disabling sets governed ports to OFF; re-enabling immediately restores ADVANCE mode at automation-defined speeds — no next-trigger wait. Use break_out_of_automation for a controlled handoff that also locks co-governed ports to safe manual speeds.

Args: device_id: The AC Infinity device code (from discover_devices). automation_id: The automation_id from list_advance_automations. dry_run: If True (default), returns the action plan without executing.

Returns: JSON with action, automation_name, automation_id, governed_ports (list of {port, port_name} dicts decoded from the automation's grouptDevType bitmasks), human_summary, dry_run, sent, and to_restore (natural-language hint for re-enabling). On failure returns {"error": "..."}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
automation_idYes
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses key behaviors: no-op if already disabled, dry_run defaults to true, disabling sets governed ports to OFF, re-enabling restores ADVANCE mode immediately. Includes live-testing date for confidence.

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 with clear sections: purpose, behavior, arguments, returns. Slightly verbose but every sentence adds value. Could be tightened without losing clarity.

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?

Covers all necessary context: preconditions, execution behavior, arguments, return format, error handling. Output schema is described adequately, making the tool fully understandable.

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?

With schema coverage at 0%, the description fully explains each parameter: device_id from discover_devices, automation_id from list_advance_automations, dry_run as boolean defaulting to true. Also details the return structure.

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 action: 'Disable a currently enabled Advance Automation.' It also notes that it reads current state and no-ops if already disabled, distinguishing it from similar tools like break_out_of_automation.

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 mentions default dry_run=True and contrasts with break_out_of_automation for controlled handoff. Provides clear instructions for when to use this tool vs. alternatives.

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