Skip to main content
Glama

Cancel hot water boost

hive_cancel_hot_water_boost
Idempotent

Stop an active hot water boost early and return the system to its previous mode. Optionally preview the exact requests without changing anything.

Instructions

Stop a hot water boost early and go back to the previous mode.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hive_cancel_hot_water_boost"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.6/5.0
Behavior3/5

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

The annotations already declare non-read-only, non-destructive, idempotent behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that the system returns to the PREVIOUS mode rather than defaulting to off — but says nothing about the no-active-boost case, error behavior, or confirmation of the resulting state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, no filler, with the action front-loaded and the resulting state as the trailing clause. Every word earns its place.

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?

Appropriate for a simple one-parameter action tool: annotations carry the safety/idempotency profile, the schema fully documents dry_run, and no output schema exists. The only meaningful gap is the undefined outcome when no boost is active.

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?

The single parameter (dry_run) is fully documented in the schema at 100% coverage, including precise semantics ('Nothing is changed'), so the description need not repeat it. The description adds no parameter meaning of its own, which is acceptable at this coverage level.

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-plus-resource ('Stop a hot water boost early') and adds the resulting state ('go back to the previous mode'), which makes the intent unambiguous. It implicitly contrasts with hive_boost_hot_water but never names a sibling or explicitly distinguishes itself from hive_cancel_heating_boost.

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?

'Stop ... early' implies the tool only applies while a boost is active, so usage is inferable rather than stated. There is no explicit when-not guidance (e.g. what happens if no boost is running) and no routing to the related cancel/boost siblings.

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