Skip to main content
Glama

iaqualink_list_schedules

Read-only

List a pool system's schedules and timers, including circuits, run days, start/stop times, and pump or chlorinator timers, so you can inspect settings before editing or deleting them.

Instructions

List a pool system’s schedules (programs/timers). iAqua (Jandy AquaLink RS) panels: the panel’s own schedule — circuit, start, stop (24-hour, plus the panel’s text) and run days, with the page/row each sits at (what iaqualink_edit_schedule and iaqualink_delete_schedule identify it by) — read through iAqualink WebTouch, the panel emulation. If WebTouch is unavailable it falls back to the iQ20 schedule list (adapter firmware 3+), trying each candidate host once and reporting which answered (probe). eXO salt chlorinators: the pump, chlorinator and aux timers (name, start/stop, enabled, rpm for variable-speed pumps). Returns supported: false with the reason when there are none to read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "<serial>"
    },
    "name": "iaqualink_list_schedules"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesSystem serial number, from iaqualink_list_systems

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that — the WebTouch-first read path, the iQ20 fallback gated on adapter firmware 3+, single-attempt host probing with the answering host reported via 'probe', and the 'supported: false' response with a reason. None of this contradicts the read-only annotation.

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 front-loaded with the core action, then expands per system family in a logical order, and every clause carries real information. It is dense with em-dashes and nested parentheticals that slow parsing, keeping it just short of a 5.

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?

With no output schema, the description carries the full burden of describing returns and does so per device family (circuit/start/stop/run days plus page and row; name, start/stop, enabled, rpm for eXO) as well as the failure shape. For a one-parameter, annotation-covered read tool this leaves nothing an agent needs missing.

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?

There is a single parameter at 100% schema coverage, and the schema already documents it as the system serial sourced from iaqualink_list_systems. The description adds no format, validation, or alternative-value information about the serial beyond what the schema states, so the baseline of 3 applies.

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 opening sentence names a specific verb and resource ('List a pool system's schedules') and then enumerates the three distinct system families covered (AquaLink RS panels, WebTouch/iQ20 fallback, eXO chlorinators) with the fields returned for each. It also distinguishes itself from iaqualink_edit_schedule and iaqualink_delete_schedule by explaining that this tool supplies the page/row identifiers those tools consume.

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?

Usage context is clear: read schedules here, then use the edit/delete siblings with the returned page/row identifiers, and expect 'supported: false' when nothing is readable. There is no explicit when-not guidance or a named alternative for listing schedules in another way, so it falls short of a 5.

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