Skip to main content
Glama

List Hive actions

hive_list_actions
Read-only

List Hive actions to review each automation’s name, enabled status, trigger, condition, action, and involved devices.

Instructions

List the Hive actions (automations set up in the Hive app, such as "when the back door opens, send a notification"): each one's name, whether it's on, and its events: what starts it (when), any condition (while) and what it does (then), with the devices involved.

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

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 safe-read profile is known. The description adds genuinely useful return-shape detail (each action's name, enabled state, and its when/while/then events with involved devices), which is valuable given no output schema, but says nothing about caching behavior beyond the parameter text or about limits on result size.

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?

Front-loaded with the verb and resource, and every clause adds content (definition of an action, returned fields, event anatomy) rather than filler. The single sentence with nested parentheticals is slightly dense but not padded.

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-shape burden and does so adequately by enumerating name, enabled state, and event structure with devices. Two fully-documented optional parameters plus read-only annotations mean little else is missing.

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% and both parameters (raw, fresh) are fully documented in the schema, including the HIVE_CACHE_SECONDS reference. The description adds nothing about either parameter, so 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+resource ("List the Hive actions") with an immediate gloss defining what an action is (an automation such as "when the back door opens, send a notification"), plus the fields returned: name, on/off, and events. It is clearly a different resource from the device/TRV/heating siblings, though it never names an alternative to contrast with.

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: the domain gloss tells an agent this is for inspecting automations rather than devices or heating, but there is no explicit when-to-use, when-not-to-use, or naming of a sibling alternative. No prerequisites are stated.

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