Skip to main content
Glama

Set heat on demand

hive_set_heat_on_demand
Idempotent

Enable or disable heat on demand for a heating zone so Hive radiator valves can turn the boiler on when their rooms fall below target, even if the thermostat isn't calling for heat.

Instructions

Turn heat on demand on or off for a heating zone. With it on, Hive radiator valves can turn the boiler on through this zone when their rooms are below target, even when the thermostat isn't calling for heat (Hive shows this as a boost with boost_reason "heat on demand"). The setting stays until changed.

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": {
      "enabled": "<enabled>"
    },
    "name": "hive_set_heat_on_demand"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneNoHeating zone (a Hive thermostat, not a TRV zone), by name or ID. Can be left out when there's only one
dry_runNoPreview only: check the call and return the exact requests it would send to Hive, without sending them. Nothing is changed
enabledYestrue to let radiator valves turn the boiler on when their rooms need heat, false to stop them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description adds the key non-schema behavioral fact: the setting persists until changed, and it manifests as a boost with a specific boost_reason. It does not address permissions or how the change is reported back, but the persistence detail is genuinely useful beyond the structured fields.

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

Conciseness4/5

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

Three sentences, front-loaded with the action and then the consequence, with no filler. The parenthetical about boost_reason is slightly dense but earns its place by disambiguating from boost tools.

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 simple boolean setter with three fully documented parameters, no output schema, and full annotation coverage, the description supplies the missing 'what happens after' context. Only permissions and confirmation/response behavior are left unaddressed, which is minor at this complexity.

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 coverage is 100% and each parameter (zone, dry_run, enabled) is already clearly described in the schema, so the schema carries the semantic load. The description adds no parameter-level detail such as zone resolution rules or what dry_run returns, leaving this at the baseline for high-coverage schemas.

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 feature ('Turn heat on demand on or off for a heating zone') and explains the resulting behavior in terms of radiator valves calling the boiler. It implicitly separates this from boost operations by noting Hive surfaces it as a boost with boost_reason "heat on demand", though no sibling tool is named directly.

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?

Usage is implied rather than stated: the description explains the condition under which the feature matters (TRV rooms below target while the thermostat isn't calling for heat), which lets an agent infer when it is appropriate. There is no explicit 'use this instead of X' routing against siblings like hive_boost_heating or hive_set_heating_mode.

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