Skip to main content
Glama

io_set_display

Show or hide an input, memory, or constant in the Loxone app and set its display unit format, such as '<v.1>°' or '%'.

Instructions

Shows or hides an input, memory or constant in the app and sets its display format, e.g. '<v.1>°' or '%'.

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": {
      "block": "<block>"
    },
    "name": "io_set_display"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNo
blockYes
visibleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It discloses that visibility can be toggled and gives format-string examples, but says nothing about permissions, whether hiding is reversible, what a null 'visible' means, or what happens if the block does not exist.

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?

A single front-loaded sentence with the effect first and the format examples last. No filler; the only weakness is that the example strings are not explicitly tied to a parameter name.

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?

For a mutation tool with no annotations, no output schema, and 0% schema coverage on three parameters, the description is thin. It covers the high-level intent but leaves parameter mapping, mutation semantics, and failure behavior entirely undocumented.

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% across three parameters, so the description must compensate, and it partially does by showing the format of the display string. It never maps parameters to names, however: it does not clarify that 'unit' carries the format string or that 'visible' controls the show/hide, leaving 'block' and 'visible' undocumented.

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 pair and resource: shows or hides an input, memory or constant, plus sets its display format. The scope ('in the app') and the example format strings make the effect concrete. It does not name or contrast with any sibling such as io_set_statistics, so it stops short of full differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use versus when-not-to-use guidance and no mention of alternatives or prerequisites. The agent must infer the call context entirely from the verb phrase; nothing tells it when this tool is the wrong choice compared to the other io_* tools.

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