Skip to main content
Glama

Cancel holiday mode

hive_cancel_holiday_mode
Idempotent

Cancel holiday mode to restore normal heating and hot water settings immediately. Use dry_run to preview the Hive requests before sending any changes.

Instructions

Cancel holiday mode, so the heating and hot water go back to their normal settings straight away.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and repeat-call profile is covered. The description adds real value by describing the device-level effect (heat and hot water revert immediately), but does not cover error behavior when no holiday mode is set or any preconditions.

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?

One sentence, front-loaded with the action and followed by its consequence. No filler, nothing to trim.

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, single-optional-parameter state-changing tool with full annotation coverage and no output schema, the description supplies the action and its visible effect, which is sufficient. Only edge-case behavior (no active holiday mode, failure mode) is unaddressed.

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?

There is a single parameter with 100% schema description coverage, so the schema fully documents 'dry_run' including its preview semantics. The description says nothing about dry_run, so it adds no meaning beyond the schema; baseline 3 applies.

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 ('Cancel holiday mode') and immediately names the effect: heating and hot water return to normal settings. An agent can distinguish it from hive_set_holiday_mode and the boost-cancel siblings by the verb alone, though no sibling is named explicitly.

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?

'so the heating and hot water go back to their normal settings straight away' implies the situation in which to call it (reverting from an active holiday schedule), but there is no explicit when-to-use/when-not guidance and no mention of the alternative hive_set_holiday_mode or what happens if holiday mode is not active.

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