Skip to main content
Glama

Get holiday mode

hive_get_holiday_mode
Read-only

Check whether holiday mode is active and see its start and end times plus the heating temperature held while you are away.

Instructions

Show whether holiday mode is set: when it starts and ends and the temperature the heating holds while you're 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_get_holiday_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, so the safety profile is covered. The description adds the useful detail of what the read returns, but says nothing about what happens when holiday mode is not set (null vs. empty) or which zone the reading applies to.

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 core verb and followed immediately by the returned fields. Nothing is redundant and no filler precedes the substance.

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 no parameters, the description must convey the return shape, and it does list the three meaningful values. The remaining gap is the not-set case, which matters for an agent deciding whether holiday mode is active.

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?

The tool takes zero parameters, so there is no per-parameter meaning for the description to add. Baseline 4 applies; the description correctly implies the call is unfiltered and returns the single holiday-mode state.

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 names a specific resource (holiday mode) and the exact fields returned: start, end, and the held temperature. It is clearly distinct from the sibling heating and schedule getters by resource name, though it never explicitly contrasts itself with them.

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 — an agent can infer this is the read path for holiday-mode configuration. There is no statement of when to use it versus hive_get_heating or hive_get_heating_schedule, and no mention of prerequisites such as authentication or an active holiday period.

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