Skip to main content
Glama

Set heating mode

hive_set_heating_mode
DestructiveIdempotent

Switch a heating zone between schedule, manual hold, and off/frost protection, or cancel a boost. Use manual only for open-ended changes with confirmation; prefer a temporary boost instead.

Instructions

Switch a zone between schedule (follow the weekly schedule), manual (hold one temperature) and off (frost protection only). Cancels a boost. Manual lasts indefinitely, so it needs confirm: true; prefer hive_boost_heating for a temporary change.

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_heating_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesschedule (follow the heating schedule), manual (hold one temperature) or off (frost protection only)
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
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
temperatureNoWith manual: the temperature to hold, in °C (from 5 in steps of 0.5, up to HIVE_MAX_TEMP). Default: the zone's current target

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important side effects: switching modes cancels a boost and manual mode lasts indefinitely. It also explains the confirmation requirement for the open-ended manual mode, which is exactly the kind of behavioral context an agent needs for a destructive operation.

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?

The description is three tight sentences with the core operation front-loaded, followed by the boost side effect and the temporary-change alternative. There is no redundant wording.

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 destructive five-parameter tool, the description covers the core operation, the main side effect, the confirmation requirement and the key alternative. It does not mention dry_run or zone omission, but those are clearly documented in the schema.

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 the input schema already documents mode, zone, confirm, dry_run and temperature in detail. The description reinforces the mode meanings and confirm requirement, but adds little parameter-level meaning beyond what the schema already provides.

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 uses a specific verb and resource: switch a zone between schedule, manual and off. It distinguishes the three modes and names the boost alternative, so an agent can identify the operation without opening the 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 explicitly routes temporary changes to hive_boost_heating and explains that manual is an open-ended change requiring confirm: true. The mode definitions also clarify what schedule, manual and off mean in practice.

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