Skip to main content
Glama
ober37

AC Infinity MCP

set_port_on

Turn a port on at full speed on AC Infinity controllers. Supports fan and on/off toggle devices; includes dry-run mode to preview the payload.

Instructions

Turn a port on at full speed (onSpead=10).

Works for fan-type and on/off toggle devices. Uses read-before-write. 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. dry_run: If True (default), returns the payload that would be sent without writing.

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

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
device), the response also includes a ``warning`` field alerting the grower.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
portYes
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, the description fully carries the transparency burden. It discloses read-before-write behavior, dry_run default, error handling, and warning conditions for disconnected ports. No contradictions.

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 sections for args, returns, and warnings. It is front-loaded with the core action. However, it is slightly verbose; some sentences could be merged 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?

Given the tool's three parameters, the output schema is described in detail, covering all returned fields, warning conditions, and error cases. The description is fully complete for an AI agent to understand correct usage and expected output.

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%, but the description adds significant meaning: device_id is exemplified, port is specified as 1-based, and dry_run's behavior and default are explained. This compensates completely for the missing schema descriptions.

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: turning a port on at full speed (onSpeed=10). It specifies the tool's applicability to fan-type and on/off toggle devices, and the sibling context (e.g., set_port_off, set_port_speed) further distinguishes its purpose.

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

Usage Guidelines3/5

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

The description mentions the types of devices it works for and the dry_run default, but does not explicitly provide when-to-use vs alternatives, when-not-to-use, or prerequisites. Usage is implied but not fully guided.

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