Skip to main content
Glama

Get heating schedule

hive_get_heating_schedule
Read-only

Retrieve a heating zone's weekly schedule, including each day's periods and target temperatures, the current target, and when it next changes.

Instructions

Show a zone's weekly heating schedule: for each day, the periods and the target temperature for each, in the home's local time. Also says what the schedule asks for now and when it next changes.

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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is to add context, which it does by disclosing the local-time presentation and the derived "now/next change" fields the caller wouldn't expect from a raw schedule. It says nothing about auth requirements or error behavior, which keeps it short of a 5.

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 sentences, front-loaded with what is returned and followed by the extra derived information; no filler or restatement of the name. Every clause contributes new meaning.

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, the description has to convey return shape and does so effectively (per-day periods, per-period target, current state, next change). The remaining gap is that temperature units are never stated, which matters for interpreting the numerals returned.

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% with a single optional, fully described zone parameter, so the baseline is 3. The description goes slightly beyond by scoping the result to "a zone's" schedule and clarifying that the returned times are in the home's local time, which affects how the caller interprets per-zone output.

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?

States a specific verb and resource ("Show a zone's weekly heating schedule") and enumerates what the result contains: per-day periods and target temperatures. The heating framing plus the sibling set (hive_get_hot_water_schedule, hive_get_heating) makes the scope distinguishable without opening a schema.

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 only implied: the description notes the schedule is shown in local time and that the result also reports the current and next target, but it never says when to reach for this versus hive_get_heating or how it relates to the hot-water schedule. The only concrete guidance (zone is optional for single-zone homes) lives in the schema, not the description.

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