Skip to main content
Glama

Get heating

hive_get_heating
Read-only

Retrieves Hive heating status for thermostats and radiator valves, including temperatures, target temperatures, modes, boost time, heat demand, schedules, and battery levels.

Instructions

Show the heating: for each heating zone (a Hive thermostat) and TRV zone (Hive radiator valves), the current temperature, target temperature, mode (schedule, manual, off or boost), boost time left, whether it's calling for heat, what the schedule asks for now and next, and thermostat or valve batteries.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn Hive's full objects instead of compact summaries (much larger)
zoneNoOnly this zone, by name or ID (default every heating zone and TRV zone)
freshNoAsk Hive again instead of using a reading from the last few seconds (HIVE_CACHE_SECONDS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the returned field inventory, which is useful context beyond the annotations. However, it does not explain the freshness/caching model (HIVE_CACHE_SECONDS, the 'reading from the last few seconds' behavior) that the schema hints at, nor why idempotentHint is false — a read that can return cached values is exactly the trait worth disclosing here.

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?

A single front-loaded sentence that leads with the action and then lists return fields; the enumeration is dense but nearly every item is a distinct value the caller cares about. It is slightly long for one sentence, but there is no filler or repetition.

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?

With no output schema and a read-only, zero-required-parameter tool, the description carries the return-value explanation well by enumerating the per-zone fields. The remaining gap is behavioral (cache freshness semantics) rather than structural, so it is close to complete for this complexity level.

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 raw, zone, and fresh parameters are already well documented in structured data. The description contributes only the default scope (all heating and TRV zones when zone is omitted), which is a modest addition beyond the schema — the baseline 3 is appropriate.

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 opens with a specific verb and resource ("Show the heating") and then enumerates the exact payload: per-zone current/target temperature, mode, boost time left, call-for-heat, schedule now/next, and battery levels. It scopes across both heating zones (thermostats) and TRV zones, which separates it from hive_get_hot_water and hive_get_heating_schedule by domain, though it never explicitly names those siblings as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no routing to alternatives, even though hive_get_heating_schedule and hive_get_overview sit in the same family and the payload here partially overlaps with the schedule tool. The only usage signal is implicit: the default (no zone parameter) reads every heating and TRV zone.

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