Turn a Shelly switch or relay channel on or off, optionally auto-reverting after N seconds. Returns the resulting channel state for local device control.
Turn a switch/relay channel on or off (optionally auto-revert after N seconds).
Returns the post-action ChannelState. Audit-logged.
| Name | Required | Description | Default |
|---|---|---|---|
| on | Yes | ||
| device | Yes | ||
| channel | No | ||
| toggle_after_s | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.3Input schema / additionalPropertiesAdded value: +falsev0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the single idempotentHint annotation, the description discloses two useful traits: the post-action ChannelState is returned and the action is audit-logged. It does not state what happens on an unknown device/channel or error behavior, but the added context is real and consistent with idempotentHint=true.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core action and followed by return and audit facts. No padding or repetition; every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be spelled out. However, with 0% schema coverage and no annotations covering permissions or failure modes, the description leaves device identification, channel defaults, and error behavior undocumented.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It maps meaning onto all four parameters semantically ('on or off' -> on, 'channel', 'after N seconds' -> toggle_after_s, 'a switch' -> device), but gives no syntax, defaults (channel default 0), or device-identifier format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Turn a switch/relay channel on or off', and adds the auto-revert option. It is clear what the tool does, though it never explicitly contrasts itself with the very similarly named sibling shelly_switch_toggle.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no prerequisites, and no mention of alternatives such as shelly_switch_toggle (toggle) versus this tool's explicit set-to-state semantics. The agent must infer the distinction from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.