Skip to main content
Glama
ober37

AC Infinity MCP

set_humidity_automation

Enable humidity-based automation on a controller port by setting minimum and maximum relative humidity thresholds. The controller adjusts fan speed to maintain humidity within the defined range.

Instructions

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

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

Args: device_id: Device code from discover_devices (e.g. "C58ZA"). port: 1-based port number. min_rh: Minimum relative humidity threshold (%), range 0–100. Sub-percent values are rounded to the nearest integer (e.g. 50.5 → 51). max_rh: Maximum relative humidity threshold (%), range 0–100. Must exceed min_rh. Sub-percent 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_rh, max_rh, dry_run, controller_type, sent, and payload (when dry_run=True). On failure returns {"error": "..."}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
portYes
min_rhYes
max_rhYes
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, dry_run behavior, threshold rounding, valid ranges, and return format. No annotations provided, so description bears full burden and meets it thoroughly.

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). Detailed but not overly verbose. A minor trim could improve conciseness, but it's effective.

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 no annotations, the description covers all behavioral aspects: read-before-write, rounding, defaults, modes. Also describes return schema. Complete for a tool of this complexity.

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 explains every parameter including device_id, port, min_rh (with rounding), max_rh (with constraint > min_rh), and dry_run (with default). Adds meaning 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 'Enable humidity automation on a port' using a specific sensor. Distinguishes itself from siblings like set_temperature_automation and set_vpd_automation by focusing on humidity.

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?

Describes the effect (switches to AUTO mode, sets thresholds) and includes details like read-before-write and dry_run default. Does not explicitly mention when not to use, but the purpose is clear.

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