Skip to main content
Glama
ober37

AC Infinity MCP

get_device_reading

Retrieve current temperature, humidity, and VPD from an AC Infinity controller by providing its device ID. Returns sensor data with timestamp.

Instructions

Get current sensor reading for a device by its AC Infinity device_id. Returns temperature, humidity, VPD, and timestamp.

Args: device_id: The AC Infinity device code (from discover_devices)

Returns: JSON example::

    {
      "device_id": "C58ZA",
      "device_name": "Towlie Tent",
      "temperature": 75.7,
      "unit": "°F",
      "humidity": 58.2,
      "vpd": 1.31,
      "timestamp": "2026-05-20T09:32:00 CDT",
      "ports": [
        {"port": 1, "name": "Inline Fan", "speed": 5},
        {"port": 2, "name": "Port 2", "speed": 0, "plug_status": "not powered"}
      ],
      "external_sensors": []
    }

Temperature and timestamp use the device's own unit preference and timezone
(from ``deviceInfo.unit`` and ``zoneId`` in the API response). Devices
without a configured timezone fall back to UTC.
``external_sensors`` excludes phantom entries (API-reported sensor slots
with no physical hardware connected — see API Quirk 20).
``plug_status`` is only present on a port entry when no current is detected,
the port is not running (speed 0 and no load), **and the port still has its
default name** (``"Port N"``). Custom-named ports are assumed to have a device
intentionally connected — ``loadState=0`` alone cannot distinguish "nothing
plugged in" from "device is off" for on/off devices. This matches the signal
used in ``get_port_status``.
On failure returns ``{"error": "...", "detail": "..."}``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes

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 thoroughly discloses behaviors: timezone/unit handling, exclusion of phantom external sensors, conditional plug_status field, and error format. This is 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose, args section, return example, and edge case notes. Every sentence adds value, and it is front-loaded with the core function.

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 complex return data and lack of annotations, the description is complete: it covers return fields, edge cases, error format, and parameter origin. The output schema presence reduces burden, but the description adds necessary context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has only a device_id string with no description. The description adds meaning by noting the device_id comes from discover_devices and showing an example. This compensates for 0% schema coverage.

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 tool gets current sensor reading for a device by device_id, listing the specific fields returned. It differentiates from siblings like get_all_device_readings by focusing on a single device.

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 implies usage for retrieving a single device's current reading, but does not explicitly mention alternatives like get_all_device_readings or when not to use it. The context is clear enough for basic guidance.

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