Skip to main content
Glama
ober37

AC Infinity MCP

get_port_status

Retrieve real-time operational status of a specific port on an AC Infinity controller, including power level, mode, and timer.

Instructions

Get the live operational status of a single port.

Reads real-time fields from the device info response: actual current power level, active automation mode, and remaining timer seconds.

Args: device_id: The AC Infinity device code (from discover_devices) port: 1-based port number

Returns: JSON example (port not powered)::

    {
      "device_id": "C58ZA",
      "port": 1,
      "port_name": "Port 1",
      "power_level": 0,
      "mode": "OFF",
      "plug_status": "not powered"
    }

``mode`` is one of: OFF, ON, AUTO, TIMER_TO_ON, TIMER_TO_OFF, CYCLE, SCHEDULE, VPD,
Automation. ``plug_status`` is only present when no current is detected on the port (the
port is not powered or nothing is connected). It is omitted when the port is running.
Only emitted for default-named ports (``"Port N"``) — custom-named ports are assumed to
have a device intentionally connected; ``loadState=0`` alone cannot distinguish "nothing
plugged in" from "device is off".
``remain_time_seconds`` is only present when a countdown timer is active (value > 0);
it is omitted when there is no active timer.
When ``mode`` is ``Automation``, the port is governed by a named Advance Automation
program in the AC Infinity app. ``automation_name`` is present only when the port is
under automation control and the governing automation name was successfully resolved;
absent otherwise.

When the port appears to have nothing connected (primary: ``portResistance == 65535``;
fallback for old firmware: default-named ``"Port N"`` with zero load, or a devType=18/22
controller), the response also includes a ``note`` field alerting the grower
(e.g. ``"Port 7 doesn't appear to have anything connected."``).

On failure returns ``{"error": "...", "detail": "..."}``.

Note on ADVANCE detection: ``isOpenAutomation==1`` in devInfoListAll is the primary
signal. For AI+ devices (no curMode field) and older firmware without isOpenAutomation,
a secondary call to getdevModeSettingList is made to check modeType.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
portYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully carries behavioral disclosure. It details conditional field presence (plug_status, remain_time_seconds, automation_name, note), handling of edge cases (unpowered ports, default vs custom names), failure response format, and ADVANCE detection logic. Extremely thorough.

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?

Front-loaded with core purpose, then detailed behavior. Slightly verbose with multiple paragraphs, but every sentence adds value. Could be more structured (e.g., bullet points for conditional fields), but still efficient.

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 schema parameters being minimal, description and output schema (assumed present) together fully cover expected behavior. Includes JSON example, error handling, and edge cases. Context signals show output schema exists, so description need not repeat return values.

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?

Schema has 0% coverage, so description adds essential meaning: device_id source (from discover_devices) and port numbering (1-based). This is clear and helpful, though could mention type or constraints (e.g., valid device IDs).

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 'Get the live operational status of a single port,' identifying specific verb and resource. Distinguishes from siblings like 'get_all_device_readings' and 'get_port_settings' by focusing on live status of a single port.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. Does not mention when not to use or suggest other tools from the sibling list. Only implies usage for live status retrieval.

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