Skip to main content
Glama

Get hot water

hive_get_hot_water
Read-only

Retrieve Hive hot water status to see if it is heating, the active mode, remaining boost time, and current or next scheduled state.

Instructions

Show the hot water: whether it's heating now, the mode (schedule, on, off or boost), boost time left, and what the schedule asks for now and next.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn Hive's full objects instead of compact summaries (much larger)
freshNoAsk Hive again instead of using a reading from the last few seconds (HIVE_CACHE_SECONDS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context by naming exactly which live values come back (heating now, boost time remaining), which explains why idempotentHint=false is plausible. However, it never mentions the caching window that governs staleness or any auth/device-offline behavior, which is the main thing an agent would want beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that opens with the resource and then enumerates returned data with no filler. It is dense but readable; the only weakness is that the parenthetical mode list and the schedule clause make it slightly listy rather than prioritized.

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?

There is no output schema, so the description must carry the return-value burden, and it does enumerate the key returned fields (heating, mode, boost time left, schedule now/next). It omits any indication of response shape or units/formatting for the boost time, which is a minor gap for a simple read tool.

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% and both optional flags (raw, fresh) carry their own descriptions, including the HIVE_CACHE_SECONDS reference. The prose adds no parameter meaning at all, so the schema does all the work and the 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?

Specific verb ("Show") plus resource ("the hot water") followed by an explicit enumeration of what is returned: heating state, mode, boost time left, schedule now/next. It is clear what the tool does, but it does not distinguish itself from the sibling hive_get_hot_water_schedule even though the description claims to report "what the schedule asks for now and next".

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: this is the read path for hot-water state. There is no statement of when to prefer it over hive_get_hot_water_schedule or hive_get_overview, and no note that the "fresh" flag should be used when a stale reading would mislead. The overlap with the schedule sibling is left for the agent to resolve.

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