acinfinity-mcp

Overview Schema Source Related Servers Discussions Admin

List automations

list_automations

Read-onlyIdempotent

Retrieve all automation programs for a controller, including schedules, port modes, and sensor thresholds, to inspect the effective rules overriding port settings.

Instructions

List the Advance Automation programs of a controller (the app's "Automations" tab).

A program is a named set of rules; each rule governs one or more ports with a mode (On/Off/Auto/Cycle/VPD), on/off power, a schedule and, for Auto/VPD, sensor thresholds. These rules override the per-port mode from get_port_settings while they run — on AI controllers this is where the real configuration lives.

Use schedule/continuous for when a rule applies: continuous=true means the app's 24/7 switch is on and the rule runs at all times (window/days are then null/empty). Thresholds: low/high are null when that trigger is not set; the underlying record is only partially reverse-engineered (see raw), so report values as decoded from the device rather than as guaranteed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`controller_id`	Yes	Controller id (`id` from list_controllers).

Output Schema

TableJSON Schema

Name	Required	Description
`rules`	Yes
`programs`	Yes	Distinct program names, in API order.
`controller_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important behavioral traits: rule override semantics, continuous=true meaning 24/7 mode with null window/days, null threshold semantics, and the caveat that the underlying record is only partially reverse-engineered. This is exactly the kind of non-obvious behavior an agent needs.

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 front-loaded with the core purpose and then adds dense, high-value context in a logical progression: program definition, override behavior, schedule semantics, and decoding caveats. Every sentence earns its place; no filler or repetition.

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?

An output schema exists, so return values need not be restated. The description covers conceptual model, runtime behavior, edge cases, and reliability caveats, making it complete enough for an agent to call this tool correctly and interpret results sensibly.

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

Parameters3/5

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

Schema description coverage is 100% and the single controller_id parameter is already documented in the schema. The description adds no further parameter-level meaning, so it meets the baseline but does not go beyond what structured input schema already provides.

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 action ('List'), the resource ('Advance Automation programs of a controller'), and the app context ('Automations' tab). It distinguishes itself from raw/settings siblings by framing these as the real configuration on AI controllers, so an agent can tell what this tool returns.

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 provides strong contextual guidance: rules override get_port_settings while running, and on AI controllers this is where real configuration lives. This implies when to prefer this tool over port-settings tools. However, it does not explicitly contrast with get_automations_raw or state when not to use this tool, so the guidance is clear but not fully explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server