Skip to main content
Glama

iaqualink_set_pump_speed_rpm

Idempotent

Set the RPM for a named Jandy AquaLink RS pump speed (600–3450) via WebTouch, with confirmation and a re-read to verify the change.

Instructions

Change the RPM of one of a Jandy AquaLink RS panel’s named pump speeds (600–3450), through WebTouch. The panel stores a typed RPM for the running speed, so a speed that is not running is run for a few seconds while it is set, and the speed that was running is switched back afterwards; the speeds are re-read to confirm. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

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>",
      "speed": "<speed>",
      "rpm": "<rpm>"
    },
    "name": "iaqualink_set_pump_speed_rpm"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpmYesNew RPM, 600–3450
speedYesA named speed as iaqualink_list_pump_speeds shows it, e.g. "Pool" or "Spa"
serialYesSystem serial number, from iaqualink_list_systems
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the panel temporarily runs a non-running speed to type the RPM, switches back the previously running speed afterwards, and re-reads speeds to confirm. It also fully specifies the confirmation protocol (client prompt or preview plus confirmToken under MCP_CONFIRM_MODE), which the annotations alone do not convey. Nothing here contradicts readOnlyHint=false, destructiveHint=false, or idempotentHint=true.

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 action, range, and channel are front-loaded in the first sentence, and the subsequent sentences cover effects and confirmation in a logical order. The confirmation sentence is long and the MCP_CONFIRM_MODE reference is dense, but no sentence is filler.

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

Completeness4/5

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

For a mutation tool with no output schema, this covers the side effects, the post-set verification, and the entire confirmation flow, which is what an agent most needs. Minor gaps remain, such as what a failure looks like, but the behavioral picture is substantially complete.

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%, so the schema already documents serial, speed, rpm, and confirmToken, including the 600–3450 range and the two-step token rules. The description reinforces the RPM constraint and the source of the speed name but adds little parameter meaning the schema does not already carry, so the baseline 3 applies.

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: change the RPM of a named pump speed on an AquaLink RS panel, with the valid range and the WebTouch channel. It is clear what the tool does, but it never distinguishes itself from the sibling iaqualink_set_pump_speed, leaving the agent to infer which of the two to call.

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 context is implied through the confirmation workflow and the reference to the WebTouch path, but there is no explicit when-to-use versus when-not guidance and no mention of the pump-speed sibling. The agent knows how the call proceeds but not why it would pick this over the alternative tool.

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