Skip to main content
Glama

Set heating schedule

hive_set_heating_schedule
DestructiveIdempotent

Change a heating or TRV zone's weekly schedule by setting per-day time and temperature periods, while leaving unspecified days unchanged; preview and confirm before replacement.

Instructions

Change a heating zone's or TRV zone's weekly schedule. In days, give the periods for the days that change, keyed by day or by weekdays, weekend or every_day (a day wins over a group); other days keep their current periods. Each day has 1 to 6 periods, each a start time (HH:MM, home's local time) and a target temperature, lasting until the next period starts (before a day's first period, the previous day's last one carries on). This replaces those days' schedule for good, so show the user the new periods and get their go-ahead first. The zone only follows it in schedule mode.

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": {
      "days": "<days>"
    },
    "name": "hive_set_heating_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesThe new periods for the days that change, keyed by day (monday ... sunday) or group (weekdays, weekend, every_day); a day wins over a group. Days left out keep their periods
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
dry_runNoPreview only: check the call and return the exact requests it would send to Hive, without sending them. Nothing is changed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is partly covered. The description adds real value beyond them: only the named days are replaced, omitted days keep their periods, and the change is permanent. It slightly restates the destructive nature that annotations already flag, which caps the score.

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?

Front-loaded with the mutation and the key routing rule (day beats group), then constraints, then the warning to confirm with the user. Every sentence adds a distinct, actionable fact with no filler.

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 destructive, nested-payload schedule writer with no output schema, the description states what changes, what is preserved, the confirmation requirement, the mode dependency, and that dry_run previews requests without sending them. An agent has everything needed to call it correctly and safely.

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 a 4 by adding meaning the schema does not, notably day-versus-group precedence ("a day wins over a group"), the 1-to-6 periods limit, and the carry-over rule where the previous day's last period extends before the first period of a day.

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?

Specific verb plus resource: "Change a heating zone's or TRV zone's weekly schedule." It is clearly distinguishable from sibling tools such as hive_get_heating_schedule (read) and hive_set_hot_water_schedule (different resource) 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 Guidelines4/5

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

It states the operational context (the zone only follows the schedule when in schedule mode) and a mandatory pre-flight step (show the user the new periods and get their go-ahead first). It does not explicitly name a read-first alternative such as hive_get_heating_schedule, but the confirmation requirement implies it.

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