Skip to main content
Glama

Switch a smart plug

hive_set_plug
Idempotent

Switch a Hive smart plug on or off by name or ID, with an optional preview that shows the exact requests before anything changes. Confirm what's plugged in before turning it off.

Instructions

Switch a Hive smart plug on or off. Check what's plugged in with the user before switching it off.

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": {
      "on": "<on>"
    },
    "name": "hive_set_plug"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYestrue to switch the plug on, false to switch it off
plugNoSmart plug, by name or ID (see hive_list_smart_devices). Can be left out when there's only one
dry_runNoPreview only: check the call and return the exact requests it would send to Hive, without sending them. Nothing is changed

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 already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds genuine non-schema context: that switching off has real-world consequences worth confirming with the user first. It says nothing about error behavior or offline plugs, which is why it isn't a 5.

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?

Two short sentences, purpose front-loaded, safety condition second. No restated name, no filler, nothing that could be cut without losing information.

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 three-parameter, non-destructive toggle with full schema coverage and no output schema, the description supplies everything essential: the action, the state semantics, and a user-confirmation rule. Only edge-case behavior (plug missing/offline, what a dry_run response looks like in practice) is left unaddressed.

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 each parameter, including dry_run and the optional single-plug default, is fully documented in the schema itself. The description adds only the indirect hint that the plug's contents matter before toggling off. With the schema doing the heavy lifting, the baseline 3 is appropriate.

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?

"Switch a Hive smart plug on or off" names a specific verb (switch) and a specific resource (Hive smart plug), with the binary state spelled out. This separates it from siblings like hive_set_light or hive_set_heating_temperature without the agent needing to open any schema.

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?

It gives a concrete pre-condition for the risky direction: confirm with the user what is plugged in before switching off. It also implicitly routes device discovery to hive_list_smart_devices via the plug parameter. It lacks explicit "when-not-to-use" or failure-case guidance (e.g., plug offline), so it stops short of a 5.

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