Skip to main content
Glama

Boost heating

hive_boost_heating

Boost a heating zone to a chosen temperature for a set number of minutes, then automatically restore the previous mode; replaces any existing boost.

Instructions

Boost a zone: heat to a temperature for a number of minutes, then go back to the previous mode. Replaces any boost already running.

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": {
      "temperature": "<temperature>"
    },
    "name": "hive_boost_heating"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneNoHeating zone or TRV zone, by name (for example "Heating" or "Bedroom") or ID. Can be left out when there's only one. See hive_get_heating
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 boost for, in minutes (default 60, at most 360)
temperatureYesTemperature to boost to, in °C (from 5 in steps of 0.5, up to HIVE_MAX_TEMP)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnlyHint false, destructiveHint false, idempotentHint false). The description adds genuinely useful behavior beyond that: the boost is time-limited, it automatically reverts to the previous mode, and a new boost supersedes any running one. What is still missing is the failure behavior (e.g. what happens if the zone is off or in holiday mode) and confirmation of the revert timing.

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?

Two compact sentences, front-loaded with the core action and followed by the side effect that matters most (reverting to the previous mode). No filler and nothing redundant with the 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 four-parameter mutation with no output schema, the description covers the essential lifecycle: set a temporary temperature, hold it for N minutes, then restore. The meaning of "previous mode" and edge cases such as boosting a zone that is currently off remain unexplained, but nothing required for a correct call is absent.

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%, with temperature, minutes, zone and dry_run all documented, including ranges and defaults. The description only restates temperature and duration in narrative form and adds no syntax or constraint detail beyond the schema, 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?

The description names a specific verb and resource ("Boost a zone") and adds the defining behavior of a boost: heat to a temperature for a number of minutes, then revert to the previous mode. That is clearly distinct from a plain setpoint change. It does not name a sibling (e.g. hive_cancel_heating_boost or hive_set_heating_temperature) to sharpen the boundary, so it falls short of a 5.

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 auto-revert behavior implies when this is appropriate instead of a permanent setpoint change, and "Replaces any boost already running" flags the interaction with an existing boost. However, there is no explicit statement of when to use this versus hive_set_heating_temperature, hive_set_heat_on_demand or hive_cancel_heating_boost, leaving the agent to infer the routing.

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