Skip to main content
Glama

Set heating temperature

hive_set_heating_temperature
Idempotent

Set a Hive heating zone's target temperature: schedule mode lasts until the next scheduled change, while manual mode holds it until changed. Confirm open-ended holds; use boost for temporary changes.

Instructions

Set a zone's target temperature. In schedule mode this lasts until the next scheduled change, like turning the thermostat dial; pass mode=manual to hold it. If the zone is off, the target is saved but nothing heats until the mode changes. Holding a temperature in manual mode (mode=manual, or a zone that is already in 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": {
      "temperature": "<temperature>"
    },
    "name": "hive_set_heating_temperature"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoAlso switch mode: manual (hold this temperature) or schedule (just until the next scheduled change, as turning the dial does)
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
temperatureYesTarget temperature in °C, from 5 in steps of 0.5, up to HIVE_MAX_TEMP (see the schema maximum)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: annotations only declare it is not read-only, is idempotent, and is non-destructive, while the description discloses that a zone in 'off' mode saves the target without heating, that schedule-mode holds expire at the next scheduled change, and that manual holds require confirm: true.

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?

Four sentences, each carrying a distinct load (scope, schedule semantics, off-zone caveat, manual/confirm rule plus alternative). The most consequential constraint and the sibling alternative are front-loaded rather than buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with no output schema, the definition covers what changes, how long it lasts, what happens when the zone is off, the safety gate, and the escape hatch to a sibling tool. Nothing an agent needs to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining cross-parameter interaction — that a zone already in manual mode triggers the confirm requirement even when mode is omitted — which no single schema property description conveys.

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?

Opens with a specific verb+resource: "Set a zone's target temperature." It also distinguishes itself from hive_boost_heating by naming that sibling and the condition that selects it, so an agent can route correctly without inspecting schemas.

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?

Gives explicit when-to-use guidance for each mode (schedule = dial-like, until next change; manual = indefinite hold), states the confirm prerequisite for open-ended changes, and names hive_boost_heating as the preferred alternative for temporary changes.

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