Skip to main content
Glama
ober37

AC Infinity MCP

set_temperature_automation

Enable temperature automation on a controller port by switching to AUTO mode and setting min/max temperature thresholds. The fan speeds up above max_temp and slows down below min_temp.

Instructions

Enable temperature automation on a port using the built-in temperature sensor.

Switches the port to AUTO mode (atType=3) and sets the temperature thresholds. The controller speeds up when temperature exceeds max_temp and slows down below min_temp. Uses read-before-write. Defaults to dry_run=True.

Pass values in the device's preferred unit (°F or °C). Call discover_devices first to check temp_unit. Valid range: 32–122°F or 0–50°C (device API cap = 50°C).

Args: device_id: Device code from discover_devices (e.g. "C58ZA"). port: 1-based port number. min_temp: Minimum temperature threshold in the device's preferred unit. Sub-degree values are rounded to the nearest integer. max_temp: Maximum temperature threshold in the device's preferred unit. Must exceed min_temp. Sub-degree values are rounded to the nearest integer. dry_run: If True (default), returns the payload that would be sent without writing.

Returns: JSON with action, device_id, port, min_temp, max_temp, unit, dry_run, controller_type, sent, and payload (when dry_run=True). On failure returns {"error": "..."}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
portYes
min_tempYes
max_tempYes
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses read-before-write behavior, default dry_run=True, controller speed-up/slow-down logic, and failure return format. No annotations exist, so description carries full burden and does so well.

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 sections for purpose, usage, args, and returns. Slightly lengthy but justified by complexity; front-loaded with main action.

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 prerequisites, behavior, parameter constraints, and return format. Output schema exists but description enriches understanding with unit and rounding details.

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?

Explains all five parameters in detail, including device_id source, port numbering, threshold constraints, rounding, and dry_run purpose. Schema provides no descriptions, so this adds significant value.

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 it enables temperature automation on a port, switches to AUTO mode, and sets thresholds. Distinguishes from sibling tools by focusing on temperature specifically.

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?

Provides guidance on unit handling (preferred unit, call discover_devices), valid ranges, and rounding. Lacks explicit alternatives but gives sufficient context for correct usage.

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