Skip to main content
Glama

io_add_virtual_input

Creates a virtual input in a Loxone Miniserver for HTTP-set values from clients like Home Assistant, with options for text/analog type, units, and app visibility.

Instructions

Adds a virtual input under 'Virtual inputs'. Values are set via HTTP (/dev/sps/io//), e.g. from Home Assistant. visu=True shows it in the app, unit is the display format (e.g. '<v.1>°'). text=True creates a text input (send the value URL-encoded; WARNING: querying /state on a text input overwrites it). desc is the name in the app. System variables are fed via an output placeholder of the system variable, not via 'source'.

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>"
    },
    "name": "io_add_virtual_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo
roomNo
textNo
unitNo
visuNo
titleYes
analogNo
max_valNo
min_valNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add genuine behavioral context: text inputs require URL-encoded sends, querying /state on a text input overwrites its value, visu controls app visibility, and system variables must be fed via an output placeholder instead of the input path. It stops short of covering duplicate-title handling, persistence, permissions, or what the call returns.

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?

Dense but well front-loaded: the creation action comes first, then value delivery, then per-flag semantics with the inline WARNING in the right place. The final sentence about system variables is somewhat cryptic and injected as an aside, but overall little is wasted.

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

Completeness3/5

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

For a 10-parameter mutation tool with no annotations and no output schema, the description provides useful behavioral hints and one warning but leaves half the parameters unexplained and says nothing about the result of the call or error cases. Adequate to attempt a call, not complete enough to call confidently with analog/min/max/room/category.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain all 10 parameters, but it only covers desc, unit, text, visu, and implicitly title via the /dev/sps/io/<title>/<value> pattern. analog, min_val, max_val, room, and category are left entirely undefined, and the mention of 'source' refers to a parameter that does not exist in the schema, adding confusion rather than clarity.

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 specific verb and resource: 'Adds a virtual input under "Virtual inputs"'. An agent can tell this creates an IO object rather than, say, a command or a display. It does not explicitly contrast with siblings like io_add_command or io_set_display, which keeps it from 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?

Implies usage through the HTTP value-setting pattern ('e.g. from Home Assistant') and the note that system variables should be wired via an output placeholder rather than this mechanism, which is a real usage steer. However there is no explicit when-to-use guidance relative to the other io_add_* tools, and no prerequisites or failure conditions are stated.

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