Skip to main content
Glama
ober37

AC Infinity MCP

get_port_settings

Retrieve the active mode, speed target, and full automation configuration for a specific AC Infinity port, including VPD, temperature, humidity, schedule, and cycle settings.

Instructions

Get the full automation configuration for a port.

Calls the getdevModeSettingList endpoint and returns the active mode, speed target, and all configured automation targets (VPD, temperature, humidity, schedule, timer, cycle).

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

Returns: JSON example (non-ADVANCE port)::

    {
      "device_id": "C58ZA",
      "port": 1,
      "mode": "AUTO",
      "speed_target": 5,
      "vpd_target_kpa": null,
      "temp_range": null,
      "humidity_range_pct": null,
      "schedule_window": null,
      "cycle_on_seconds": 300,
      "cycle_off_seconds": 60
    }

When ``mode`` is ``"ADVANCE"``, ``speed_target`` is null (an automation governs
the port), and the response includes three additional enrichment fields:

- ``automation_running``: ``true`` if the governing automation has
  ``run_state=True``; ``false`` if an automation was found but none active;
  ``null`` when the secondary API call failed (degraded path).
- ``automation_configured``: ``true`` if the automations list is non-empty;
  ``false`` if empty; ``null`` when degraded.
- ``human_summary``: grower-readable description of the ADVANCE state.
  Three variants:
  - Governing found: ``"Port is running under 'Name' automation (target
    speed: N, current live speed: M). The automation is active."``
  - All disabled: ``"Port is in automation mode, but all automations are
    disabled. The port hasn't fully released. Ask me to list your
    automations for details."``
  - Degraded: ``"Port is in ADVANCE automation mode. Automation details
    could not be retrieved."``

``current_speed`` reflects the live fan speed from the device.
``automation_name``/``automation_id`` are populated from the governing
automation (or null if none active or secondary lookup degrades).
``automation_on_speed`` is read from the port group of the governing
automation whose ``grouptDevType`` bitmask covers this port (bitmask-matched);
null when no governing automation, no matching port group, or degraded.
``vpd_target_kpa`` is non-null only when VPD automation is active.
``temp_range`` / ``humidity_range_pct`` are non-null only when those
thresholds are enabled. ``schedule_window`` times are in device local time
(not UTC).

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 includes a staleness-aware ``note`` field.
On the non-ADVANCE path, ``human_summary`` is overridden with a staleness statement
and ``note`` is set to a redirect hint, so the response doesn't contradict itself
(e.g. "Humidity automation: 60–100%") for a port with nothing connected.
On the ADVANCE path, ``human_summary`` is preserved (it already describes the
automation state) and only ``note`` is appended.
On failure returns ``{"error": "...", "detail": "..."}``.

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?

No annotations provided, but description fully compensates by disclosing endpoint, both normal and ADVANCE modes, edge cases (disconnected ports), staleness handling, error format, and enrichment fields. Highly transparent.

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 (Args, Returns, examples) and front-loaded purpose. Slightly verbose due to detailed edge-case explanations, but each sentence adds value. Good balance of completeness and readability.

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 the tool's complexity (two modes, multiple fields, edge cases) and presence of output schema, description covers all necessary aspects: return values, failure handling, staleness, and human_summary variants. No gaps.

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?

Schema has 0% description coverage, yet description adds clear meaning: device_id is 'AC Infinity device code (from discover_devices)' and port is '1-based port number'. Provides essential context beyond 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?

Clearly states 'Get the full automation configuration for a port' with specific verb and resource. Differentiates from siblings like set_port_mode and get_port_status by focusing on full automation configuration.

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?

Implies usage context by detailing return values (mode, speed, automation targets). Lacks explicit alternatives or when-not-to-use guidance, but the description is informative enough for an agent to infer appropriate use cases.

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