Skip to main content
Glama

Turn a Hive action on or off

hive_set_action
Idempotent

Turn a Hive automation on or off so it runs when its trigger fires. It does not run the action on demand; actions are created and edited in the Hive app.

Instructions

Turn a Hive action (an automation from the Hive app) on or off. This doesn't run it: an action that's on runs when its trigger happens. Actions can only be created or edited in the Hive app.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "enabled": "<enabled>"
    },
    "name": "hive_set_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesThe action, by name or ID (see hive_list_actions)
dry_runNoPreview only: check the call and return the exact requests it would send to Hive, without sending them. Nothing is changed
enabledYestrue to turn the action on, false to turn it off

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare non-read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond that: toggling does not execute the action, and the action fires only on its trigger, which prevents a common misuse. It does not cover error behavior for unknown action names or side effects of disabling an active action.

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?

Three short sentences, front-loaded with purpose and followed by the non-obvious behavioral caveat. Every sentence carries information the agent needs; nothing is padding.

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 simple 3-parameter toggle with no output schema and full schema coverage, the description covers purpose, the key semantic caveat, and creation constraints. Only minor gaps remain, such as behavior on an unrecognized action name.

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 action, enabled, and dry_run are all fully documented in the schema itself. The description adds no additional meaning about parameter values or formats beyond what the schema provides, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (turn on/off) and a precisely defined resource (a Hive action, glossed as 'an automation from the Hive app'), which cleanly separates it from the sibling hive_set_light/plug/heating tools that control devices rather than automations. The parenthetical definition removes ambiguity about what an 'action' is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description sets clear usage boundaries: it explicitly says the tool does not run the action, and that actions can only be created or edited in the Hive app, so the agent knows not to look for creation/editing elsewhere. It lacks an explicit pointer to hive_list_actions for discovery, though that appears in the schema description.

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