Skip to main content
Glama

iaqualink_set_onetouch

Idempotent

Turn a Jandy AquaLink OneTouch scene on or off by number or label after confirmation; press the panel toggle only when needed, then re-read scenes to verify the requested state.

Instructions

Turn a Jandy AquaLink RS panel’s OneTouch scene on or off (by number 1–6, onetouch_, or its label from iaqualink_list_onetouch), through WebTouch. The panel button is a toggle, so it is pressed only when the scene is not already in the requested state; the scenes are re-read afterwards to confirm. A scene switches several pieces of equipment at once, as configured on the panel. The toggle press was not exercised in the live capture. 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>",
      "onetouch": "<onetouch>",
      "on": "<on>"
    },
    "name": "iaqualink_set_onetouch"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYestrue = run the scene, false = stop it
serialYesSystem serial number, from iaqualink_list_systems
onetouchYesScene number (1–6), onetouch_<n>, or label
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

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: explains that the panel button is a toggle pressed only when the scene is not already in the requested state, that scenes are re-read afterwards to confirm, and that a scene changes multiple pieces of equipment. It also honestly flags that the toggle press was not exercised in the live capture.

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-loads the purpose in the first sentence, then layers toggle semantics, safety caveat, and confirmation flow in a logical order. Slightly long, but each sentence (including the confirmation fallback detail) carries operational information the agent needs.

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?

For a mutating tool with a two-phase confirmation flow, no output schema, and an open-world remote panel, the description covers everything an agent needs: state-checking behavior, post-write verification, and the exact confirmation protocol including the fallback token path.

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 baseline is 3; the description adds that onetouch accepts a number 1–6, onetouch_<n>, or a label obtained from iaqualink_list_onetouch, and explains the multi-equipment effect of the on flag. The confirmToken semantics are already fully covered in the schema, so no further value is added there.

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 ('Turn a Jandy AquaLink RS panel's OneTouch scene on or off') and describes the identifier forms accepted. It also distinguishes itself from the equipment-level siblings by noting 'A scene switches several pieces of equipment at once, as configured on the panel.'

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?

Points the agent at iaqualink_list_onetouch for labels and implies scene-level control versus individual equipment switching. It does not explicitly state when to prefer iaqualink_set_equipment or iaqualink_set_aux instead, leaving that comparison to inference.

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