Skip to main content
Glama
ober37

AC Infinity MCP

get_all_device_readings

Get current sensor readings for all AC Infinity controllers at once, providing a complete status overview with readings keyed by device ID.

Instructions

Get current sensor readings for all AC Infinity devices. Useful for a full status check across all controllers. Returns a list of readings keyed by device_id.

Returns: JSON with "readings" list — one entry per device, same shape as get_device_reading. Devices that fail to parse individually include an "error" key instead of sensor fields. ports[].plug_status is present on not-powered port entries (same loadState == 0 AND speak == 0 condition as get_device_reading, and only on default-named "Port N" ports); omitted otherwise. external_sensors excludes phantom entries (API-reported sensor slots with no physical hardware connected — see API Quirk 20). On auth/API failure returns {"error": "...", "detail": "..."}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden and excellently discloses return format, device-level error handling, port_status condition, external_sensors filtering, and auth/API failure behavior.

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 opening sentence followed by detailed return information. Every sentence adds value and is appropriately concise.

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 has zero parameters and no annotations but an output schema, the description is highly complete, covering purpose, return format, error cases, and special conditions.

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 tool has zero parameters, so baseline is 4. No parameter info needed.

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 'Get current sensor readings for all AC Infinity devices' with a specific verb and resource. It distinguishes itself from the sibling tool 'get_device_reading' which targets 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 says 'Useful for a full status check across all controllers', implying when to use. However, it does not explicitly mention when not to use or directly reference the alternative single-device tool.

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