Skip to main content
Glama

block_set_inverted

Invert or restore a Loxone block input, making a free inverted input permanently on (for example, to lock something).

Instructions

Inverts an input of a block or removes the inversion. A free, inverted input is permanently on (e.g. to lock something).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
blockYes
invertedNo
connectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one valuable domain fact, that a free inverted input is permanently on, but says nothing about what happens if the input is already connected, whether the call is idempotent, what errors are raised, or what permissions are needed for a mutation.

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 that front-load the action and follow with the semantic consequence. No filler or redundancy.

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?

A mutation tool with no annotations, no output schema, and zero documented parameters. The description would need to explain the block/connector pairing and the inverted flag's effect to be sufficient; the single lock example is not enough to call it reliably.

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?

Four parameters with 0% schema description coverage. The description only obliquely hints at the 'inverted' flag ('or removes the inversion') and says nothing about 'block', 'connector', or 'page' — notably that connector identifies which input is targeted, which is the crux of the call.

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: inverting (or un-inverting) an input on a block. The alternation between 'inverts' and 'removes the inversion' makes the operation clear, though it does not explicitly separate itself from block_set_params or block_connect, which may also affect input state.

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?

Offers an implied use case ('to lock something') but never says when to prefer this over sibling tools that configure block inputs, nor any precondition such as the input needing to be free/unconnected. The agent must infer the rest.

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