Skip to main content
Glama

iaqualink_check_panel

Read-only

Check whether an iAqua system is reachable and see its panel state: cloud online flag, current screen, open dialog, and schedule Edit mode with unsaved changes. Use when tools disagree or time out.

Instructions

Check whether an iAqua (Jandy AquaLink RS) system is reachable and what its panel is showing: the cloud online flag, then — over WebTouch — the current screen, any open dialog, and whether the schedule screen is in Edit mode with unsaved changes. Use it when the app, WebTouch and the other tools disagree, or a schedule/OneTouch tool reports a dialog or a timeout. Sends only the start-up press the WebTouch page sends when it loads (in Edit mode the panel answers it with its "must be saved" dialog); presses nothing else and changes no setting.

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_check_panel"
  }
}

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 declare readOnlyHint=true and openWorldHint=true, but the description adds material context beyond them: it discloses that a start-up press IS sent over WebTouch, that in Edit mode the panel answers with a 'must be saved' dialog (a potentially confusing side effect), and that nothing else is pressed or changed. This pre-empts misinterpretation of the response and confirms the read-only claim.

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?

Well front-loaded: purpose first, then usage triggers, then the side-effect caveat. The single dense paragraph is efficient, though the em-dash-heavy third sentence packs several clauses and could be split for faster scanning.

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?

There is no output schema, and the description compensates by enumerating precisely what the tool reports (online flag, current screen, open dialog, Edit-mode state). For a read-only diagnostic with one required parameter, nothing an agent needs to call it correctly is 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?

Schema description coverage is 100% and the single 'serial' parameter is already documented with its source (iaqualink_list_systems) and a pattern constraint. The description adds no further parameter meaning, which is the expected baseline when the schema carries the full burden for a one-param tool.

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?

States a specific verb-and-resource pair ('Check whether an iAqua (Jandy AquaLink RS) system is reachable') and enumerates exactly what is inspected: cloud online flag, current screen, open dialog, and schedule-screen Edit mode with unsaved changes. An agent can distinguish this diagnostic probe from iaqualink_get_status and iaqualink_healthcheck based on the described outputs alone.

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?

Gives concrete triggering conditions: when the app, WebTouch and other tools disagree, or when a schedule/OneTouch tool reports a dialog or timeout. It does not explicitly state when NOT to use it (e.g., for routine status polling prefer iaqualink_get_status), so the alternative-routing is implied rather than spelled out.

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