Skip to main content
Glama
ober37

AC Infinity MCP

discover_devices

Retrieve a list of your AC Infinity devices with their IDs, names, and online status to use in other tools.

Instructions

Discover all AC Infinity devices from the cloud API. Returns device IDs, names, and online status. Use this to find device_ids for use in other tools.

Returns: JSON example::

    {
      "devices": [
        {"device_id": "C58ZA", "device_name": "Towlie Tent", "status": "online"},
        {"device_id": "D91XB", "device_name": "Veg Tent",    "status": "online"}
      ]
    }

Empty account returns ``{"devices": [], "message": "No devices found"}``.
On failure returns ``{"error": "...", "detail": "..."}``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses all behavioral traits: it is a read-only discovery operation, returns a list of devices with ID and status, and handles empty accounts and errors with specific response structures. This gives agents full transparency about the tool's behavior and error handling.

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 extremely concise, front-loading the purpose in the first sentence and using a structured format with examples. Every sentence adds value, and there is no redundant information.

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 zero parameters and the presence of an output schema, the description is complete. It covers all necessary information: purpose, output format, error cases, and guidance on using the results. There are no gaps for a simple discovery tool.

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?

Since there are no parameters, the baseline is 4. The description adds value by explaining the purpose of the output (device_ids for other tools) and providing example responses, making the tool's usage clear despite no input parameters.

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 'Discover all AC Infinity devices from the cloud API' and outlines the return values (device IDs, names, online status) and the purpose of finding device_ids for other tools. This distinguishes it from sibling tools that perform actions on devices.

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 explicitly says 'Use this to find device_ids for use in other tools,' providing clear guidance on when to invoke it. It does not state exclusions, but the context of sibling tools makes it evident this is the primary device listing 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