Skip to main content
Glama

List radiator valves

hive_list_trvs
Read-only

List Hive radiator valves grouped by zone, showing each zone's temperature, target and mode plus every valve's battery, signal, online status, calibration, mounting and child lock.

Instructions

List the Hive radiator valves (TRVs) by zone: each zone's temperature, target and mode, and each valve's battery, signal, online status, calibration, mounting and child lock.

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

Input Schema

NameRequiredDescriptionDefault
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 safety is covered and the description merely needs to add context. It usefully details the returned fields, but it never explains that results may come from a short-lived cache (HIVE_CACHE_SECONDS), which is the notable behavior behind the 'fresh' flag and the non-idempotent hint.

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?

One front-loaded sentence with no filler; the field enumeration is dense but each item conveys real information about the response. Slightly list-heavy, but nothing is redundant.

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, the description carries the return-value burden and does so by naming the per-zone and per-valve fields. For a read-only list tool the only meaningful omission is cache/freshness semantics.

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 optional parameter with 100% schema description coverage, so the baseline is 3. The description does not reinforce or contextualize 'fresh' beyond what the schema already says about HIVE_CACHE_SECONDS.

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 ('List the Hive radiator valves (TRVs) by zone') and enumerates the per-zone and per-valve fields returned, which clearly separates it from heating, hot-water and generic device siblings. It stops short of naming an alternative tool, but the resource is distinctive enough for correct selection.

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 implied by the resource: call it to inspect TRV state. There is no explicit when-to-use versus hive_list_devices or hive_get_heating, and no mention of the caching tradeoff that the 'fresh' parameter exists to control, so the agent must infer the freshness decision from the schema alone.

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