Skip to main content
Glama
ober37

AC Infinity MCP

set_port_speed

Set fan or dimmer speed (1-10) on a specific port of an AC Infinity controller. Use dry_run to preview changes before applying.

Instructions

Set fan or dimmer speed on a specific port.

Uses read-before-write: reads current mode settings then overlays the new speed value. Defaults to dry_run=True — set dry_run=False to write to the device.

Args: device_id: Device code from discover_devices (e.g. "C58ZA"). port: 1-based port number. speed: Target speed 1–10 (10 = full speed). dry_run: If True (default), returns the payload that would be sent without writing. Set to False to execute the change.

Returns: JSON with action, device_id, port, speed, dry_run, controller_type, sent, and payload (when dry_run=True).

When the port is in OFF mode (atType=0 or atType=1) at call time, the
response also includes a ``warning`` field telling the grower to ask
Claude to switch the port to ON mode to activate it. The speed is stored
on the controller but the port will not run until the mode is changed.

Example (dry_run=True)::

    {
      "action": "set Exhaust Fan (Port 2) speed to 5",
      "device_id": "C58ZA",
      "port": 2,
      "speed": 5,
      "dry_run": true,
      "controller_type": "legacy",
      "sent": false,
      "payload": { ... }
    }

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
portYes
speedYes
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully carries the burden of disclosing behavior. It explains the read-before-write approach, default dry_run=True, the response format including a warning for OFF mode, and failure output.

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 Args, Returns, and an Example section, but it is somewhat lengthy. While every sentence adds value, a slightly more condensed version could be possible while retaining 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?

The description fully covers the tool's complexity, including edge cases (OFF mode), dry_run behavior, return values, and error handling. It provides sufficient context for correct invocation, given the output schema enriches this further.

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 coverage is 0%, so the description must fully explain parameters. It does so clearly: device_id (from discover_devices), port (1-based), speed (1-10), dry_run (boolean, default true). This adds 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 action as 'Set fan or dimmer speed on a specific port', with a specific verb and resource. It distinguishes itself from sibling tools like set_port_mode and set_port_on/off by focusing on speed setting.

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 provides clear context for using the dry_run parameter and warns about the OFF mode requirement, but it does not explicitly state when to use this tool versus alternatives like set_port_mode. The guidance on dry_run usage is strong.

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