Skip to main content
Glama

List Hive devices

hive_list_devices
Read-only

List Hive devices such as hubs, thermostats, valves, plugs, bulbs and sensors with online status, battery, signal, model and firmware. Filter by device type, low battery or offline state.

Instructions

List the Hive hardware: hub, thermostats, boiler module, radiator valves (TRVs), plugs, bulbs and sensors, with online status, battery level, signal strength, model and firmware. Filter by type, low battery or offline.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn Hive's full objects instead of compact summaries (much larger)
typeNoOnly devices of this type, for example trv, thermostatui, boilermodule, hub, activeplug, warmwhitelight, contactsensor
freshNoAsk Hive again instead of using a reading from the last few seconds (HIVE_CACHE_SECONDS)
offlineNoOnly devices Hive says are offline
low_batteryNoOnly battery devices at or below 25%

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, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds value by enumerating the per-device attributes returned (online status, battery, signal, model, firmware), which partly substitutes for the missing output schema. It omits any prose about the caching/freshness behavior implied by idempotentHint=false, which is only explained inside the schema.

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?

Two sentences, front-loaded with the resource and its attributes followed by the filtering capability, with essentially no filler. The device enumeration is long but earns its place by mapping to plausible `type` values such as trv and boilermodule.

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 parameterless, read-only list tool with no output schema, the description is nearly sufficient: the returned fields are named in prose, compensating for the absent return schema. Remaining gaps are the lack of sibling routing guidance and the unexplained cache semantics behind idempotentHint=false.

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 description coverage is 100%, so the schema already explains all five parameters, including the 25% battery threshold and HIVE_CACHE_SECONDS. The description's 'filter by type, low battery or offline' only restates three of those filters without adding syntax or semantics, so the baseline of 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?

The description opens with a specific verb+resource ('List the Hive hardware') and enumerates concrete device classes and returned attributes, so an agent knows exactly what comes back. It does not distinguish itself from overlapping siblings like hive_list_trvs or hive_list_smart_devices.

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?

'Filter by type, low battery or offline' implies the query use cases, giving enough context to know it is the general enumeration tool. However, it never states when to prefer it over the more targeted hive_list_trvs or hive_list_smart_devices siblings, leaving that routing decision to inference.

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