Skip to main content
Glama

Set holiday mode

hive_set_holiday_mode
Destructive

Set a holiday heating hold for a chosen date range (up to 60 days) so the home stays at one temperature while away, then resumes its normal schedule; existing holiday mode is replaced.

Instructions

Set holiday mode: from start (default now) until end, the heating holds one temperature, then the normal settings resume. It lasts at most 60 days. Replaces any holiday mode already set. Confirm the dates and temperature with the user first.

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": {
      "end": "<end>",
      "temperature": "<temperature>"
    },
    "name": "hive_set_holiday_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesWhen it ends and the normal schedule resumes, as YYYY-MM-DD or YYYY-MM-DDTHH:MM in the home's local time; at most 60 days after the start
startNoWhen holiday mode starts, as YYYY-MM-DD or YYYY-MM-DDTHH:MM in the home's local time (default now)
dry_runNoPreview only: check the call and return the exact requests it would send to Hive, without sending them. Nothing is changed
temperatureYesTemperature to keep the home at while away, in °C (from 5 in steps of 0.5, up to HIVE_MAX_TEMP; frost protection is usually 7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description earns credit by explaining what that destruction means: an existing holiday mode is replaced and normal schedules resume at the end. It also adds the 60-day ceiling as a behavioral constraint. It does not cover failure modes, auth needs, or what happens to in-progress boosts/schedules, which keeps it from 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?

Three short sentences, front-loaded with the effect and scope, followed by the limit, the overwrite behavior, and the confirmation requirement. No filler or redundancy.

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 destructive, non-idempotent mutation with no output schema, the description supplies the essential context an agent needs: duration semantics, overwrite behavior, resumption of normal settings, and a required user confirmation step. Minor gaps remain around error conditions and permissions, but nothing critical to correct invocation is missing.

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%, so the schema already documents all four parameters including the 'now' default and the 60-day cap; the description largely restates these ('from start (default now) until end', 'at most 60 days'). It adds the semantic point that the temperature is held constant while away, but no new format or edge-case guidance, so 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?

States a specific verb and resource ('Set holiday mode') and immediately explains the mechanism: heating holds one temperature from start to end, then normal settings resume. It does not name the sibling alternatives (hive_cancel_holiday_mode, hive_get_holiday_mode) explicitly, so it falls short of full sibling differentiation, but the operation is unmistakable.

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?

Provides one concrete procedural guideline ('Confirm the dates and temperature with the user first') and notes that it replaces any existing holiday mode, which implicitly distinguishes it from cancel/get variants. However, it never states when not to use it or points to a named alternative, so guidance is implied rather than explicit.

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