Skip to main content
Glama

Boost hot water

hive_boost_hot_water

Boost hot water for a set number of minutes, then automatically return to the previous mode. Use dry_run to preview Hive requests without making changes.

Instructions

Heat the hot water now for a number of minutes, then 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_boost_hot_water"
  }
}

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
minutesNoHow long to heat the water for, in minutes (default 60, at most 360)

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?

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds a genuinely useful non-annotated fact: the system automatically reverts to the previous mode when the timer expires. It stops short of saying what happens if a boost is already running, whether the boost overrides the schedule, or that hive_cancel_hot_water_boost ends it early.

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?

A single front-loaded sentence: the action comes first, then duration, then the auto-revert consequence. No filler and nothing repeated from the title or schema.

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 two-parameter, non-destructive action tool with a fully described schema and annotations, the description covers what the tool does and its key side effect. Minor gaps remain around the presence of an existing boost and early cancellation, but nothing essential for calling it correctly is missing.

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 both the minutes range (1-360, default 60) and dry_run's preview semantics are already fully documented in the schema. The description only restates that a number of minutes is involved and adds no format or edge-case meaning beyond it; 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 (heat the hot water) plus the two defining traits: immediate action and a bounded duration. The 'go back to the previous mode' clause distinguishes it from a permanent mode change, but it never names hive_set_hot_water_mode or hive_cancel_hot_water_boost as the contrasting siblings.

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?

The phrase 'heat the hot water now for a number of minutes' implies the use case (temporary manual boost rather than a schedule or mode change), but there is no explicit when-to-use/when-not guidance and no mention of the cancel sibling or what to do if a boost is already active.

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