Skip to main content
Glama

iaqualink_get_status

Read-only

Retrieve the current pool and spa status for one iAqualink system, covering temperatures, set points, pumps, heaters, circuits, lights, and chlorinator readings.

Instructions

Get the current pool/spa status of one iAqualink system: air, pool and spa temperatures, heater set points, pumps, heaters (pool/spa/solar), freeze protection, aux circuits and lights (with names), and — where the system reports them — salt chlorinator output, boost, salinity, pH and ORP. Readings are cached for a few seconds to stay polite to iAqualink.

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

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands; "raw" returns the upstream payload unprojected. compact = normalized status; full = plus aux/light details and the unprocessed entries; raw = iAqualink’s responses untouched.
serialYesSystem serial number, from iaqualink_list_systems

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value beyond that by disclosing the few-second caching window (important for an agent deciding whether to re-poll) and by flagging with 'where the system reports them' that some fields are conditionally present. It says nothing about error behavior for an unknown serial or what happens when a device is offline.

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?

Front-loaded with the verb and resource, and the second sentence about caching is short and earns its place. The long middle enumeration is dense but justified because no output schema exists. It reads as one sprawling sentence, which costs a little in scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, a fully documented schema, and no output schema, the description does well by enumerating return fields and noting caching. It is not fully complete, though: nothing explains failure modes, what a 'raw' view looks like when upstream returns an error, or whether stale cached data is flagged. For a status-reading tool that agents will likely poll, that gap is minor but real.

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?

Schema coverage is 100%, so the schema already carries the serial lookup source and the compact/full/raw view semantics. The description contributes complementary meaning, particularly that optional upstream data may be absent, which prepares the agent for missing fields. The baseline for full coverage is 3, and the conditional-fields caveat is a meaningful addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Get the current pool/spa status of one iAqualink system' — then enumerates exactly which readings come back (temperatures, set points, pumps, heaters, freeze protection, aux/lights, chlorinator). That enumeration makes the read-only status reader easy to distinguish from the mutation siblings. It stops short of naming near-neighbors like iaqualink_healthcheck or iaqualink_check_panel, so the differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool is for reading the current state of a single system. The required serial is documented in the schema as coming from iaqualink_list_systems, which provides a useful entry point. However, there is no explicit when-to-use versus healthcheck/check_panel, and no stated exclusions or call-order guidance.

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