Skip to main content
Glama

io_add_command

Adds a virtual output command under an existing Loxone virtual output (default 'Home Assistant'), including optional on/off URLs and immediate page/source wiring.

Instructions

Adds a virtual output command under an existing virtual output (default 'Home Assistant'), e.g. a push: cmd_on='/api/webhook/?msg=Text'. With source and page it is wired there right away (output placeholder).

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": {
      "title": "<title>",
      "cmd_on": "<cmd_on>"
    },
    "name": "io_add_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
titleYes
cmd_onYes
parentNoHome Assistant
sourceNo
cmd_offNo
source_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden; it does disclose useful traits the schema cannot: the default parent, that supplying source and page wires the command immediately ('output placeholder'), and the shape of cmd_on. It omits permissions, what happens when source/page are omitted, and the meaning of cmd_off/source_key, leaving sizeable gaps.

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 compact sentences with the core action front-loaded and the example inlined. The webhook example is dense and assumes domain knowledge, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Seven parameters, 0% schema coverage, no annotations, and no output schema — the description covers only about half the parameters and never explains return/result behavior or failure modes. For a mutation tool with that little structured support, this is under-specified.

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 0%, so the description must compensate. It adds meaning for parent (default 'Home Assistant'), cmd_on (URL-style command example), and source/page (immediate wiring), but says nothing about cmd_off or source_key and does not clarify title semantics.

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?

States a concrete verb+resource: adding a 'virtual output command' beneath an existing virtual output, and names the default parent 'Home Assistant'. It also gives a concrete example (a push webhook). It stops short of differentiating itself from sibling io_add_virtual_input or notification_add, so not a 5.

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 tool presupposes an existing virtual output to attach to, and the example hints at push-notification use cases. There is no explicit when-to-use vs alternative (e.g. io_add_virtual_input, notification_add) and no when-not guidance.

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