Skip to main content
Glama
ober37

AC Infinity MCP

by ober37
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_historical_readings

Retrieve historical temperature, humidity, VPD, and port readings from AC Infinity controllers over a date range with customizable sampling intervals.

Instructions

Query AC Infinity environment data across a date range with configurable sampling.

Args: device_id: The AC Infinity device code (from discover_devices) start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format sample_interval: Bucket size for averaging readings. Use "raw" for all records unmodified, or a duration string like "1m", "5m", "15m", "30m", "1h", "2h", "6h", "12h", "1d". "daily" is accepted as an alias for "1d". Default: "1h" (one averaged reading per hour). time_start: Optional UTC time filter in HH:MM format (e.g., "16:00"). If provided, only readings at or after this time are returned. Invalid HH:MM strings return a structured error. Note: time_start/time_end filters are in UTC. Use discover_devices to get the device's timezone for conversion. time_end: Optional UTC time filter in HH:MM format (e.g., "16:15"). If provided, only readings at or before this time are returned. Invalid HH:MM strings return a structured error.

    When both bounds are set and time_start > time_end (e.g. "22:00"–"06:00"),
    the window crosses midnight: the OR of [time_start, 24:00) and
    [00:00, time_end] is returned.

Returns: JSON with "readings" list and "statistics" summary. Each reading contains timestamp, temperature_c/f, humidity, vpd, and ports list. Statistics include min/avg/max per metric across the returned window. If any readings were dropped because their timestamps could not be parsed, the response also includes "dropped_readings" (count) and "drop_reason". See docs/API.md for full shape.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
start_dateYes
end_dateYes
sample_intervalNo1h
time_startNo
time_endNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Without annotations, the description carries full burden. It explains return format (readings, statistics, dropped_readings), error structure, and crossing midnight logic for time filters. It also notes timezone conversion hints. Missing rate limits or auth details, but overall transparent.

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 and Returns sections. It is fairly long but every sentence provides unique guidance. Could be slightly more concise, but no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, no annotations, and an output schema (though not shown), the description covers return shape, error cases, and references full docs. It is complete for a query tool, though could mention pagination or rate limits.

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 description coverage is 0%, so description must compensate. It explains each parameter in detail: device_id source, date formats, sample_interval with examples and default, time_start/time_end format with crossing midnight logic and error handling. This adds significant value 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 states 'Query AC Infinity environment data across a date range with configurable sampling,' which is a specific verb+resource+scope. It clearly distinguishes from sibling tools like get_all_device_readings and get_device_reading.

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 using device_id from discover_devices and gives format hints, but does not explicitly state when to use this tool vs alternatives. Usage is implied but not guided with exclusions or comparisons.

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