Skip to main content
Glama

Set hot water mode

hive_set_hot_water_mode
Idempotent

Set Hive hot water to on, off, or schedule, and cancel an active boost. Indefinite "on" requires confirmation to prevent unintended open-ended heating.

Instructions

Switch the hot water on (it stays on until changed), off, or back to its schedule. Cancels a boost. For a limited time, use hive_boost_hot_water instead of on. On lasts indefinitely, so it needs confirm: true.

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": {
      "mode": "<mode>"
    },
    "name": "hive_set_hot_water_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYeson (stay on until changed), off, or schedule (follow the hot water schedule)
confirmNoMust be true for heating mode manual or hot water mode on, which last indefinitely (until something changes them). Only set it once the user has agreed to an open-ended change; for a temporary one, boost instead
dry_runNoPreview only: check the call and return the exact requests it would send to Hive, without sending them. Nothing is changed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations cover safety (readOnlyHint false, idempotent, non-destructive), and the description adds real behavioral context: 'on' persists until changed, so it requires confirm: true, and the call cancels any active boost. The persistence and boost-cancellation semantics are not derivable from the annotations alone. It stops short of describing the response payload, but there is no output schema to lean on either.

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?

Four short sentences, front-loaded with the primary action and its states, followed by the alternative route and the confirm requirement. The persistence of 'on' is stated twice (in the first and last sentences), which is slight redundancy, but nothing else is wasted.

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 three-parameter mutation tool with no output schema, the definition covers the modes, the open-ended-change gate, the boost alternative, and the side effect on existing boosts. Only the dry_run behavior and the shape of the result are left to the schema, which documents dry_run adequately.

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 schema already documents all three parameters, including the confirm gate and dry_run preview. The description's mode explanation largely restates the enum values, so it adds little meaning beyond what the schema provides. The routing hint toward boost is useful but belongs to usage rather than parameter semantics.

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 description names a specific verb (set/switch) and resource (hot water), and enumerates the three target states: on, off, and schedule. It explicitly distinguishes itself from the sibling hive_boost_hot_water, so an agent can choose between them without inspecting either schema.

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

Usage Guidelines5/5

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

It states exactly when to prefer the alternative: 'For a limited time, use hive_boost_hot_water instead of on.' It also notes that this tool cancels an existing boost, which clarifies the relationship with the cancel-boost sibling. Both the when-to-use and the when-to-use-something-else conditions are explicit.

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