Skip to main content
Glama

block_add

Add a new logic block of a specified catalog type to a Loxone page, placing it inside the sheet without overlap and optionally applying parameter values.

Instructions

Adds a new logic block of a catalog type to a page (placed inside the sheet, not overlapping), optionally with parameter values.

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": {
      "page": "<page>",
      "type": "<type>",
      "title": "<title>"
    },
    "name": "block_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
pageYes
typeYes
titleYes
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose meaningful behavior: the block is placed inside the sheet and non-overlapping, implying automatic positioning when coordinates are omitted. However, it says nothing about persistence, side effects, permissions, or what is returned for a mutation tool with no output schema.

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 no filler; the creation action leads and the placement constraint follows. The trailing parenthetical is dense but still readable, so nothing meaningful needs cutting.

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 6-parameter mutation tool with no annotations and no output schema, the description leaves key gaps: the required 'title' semantics, what the tool returns (presumably a new block identifier), and whether the block is immediately live in the project or requires a separate build step. Sibling tools like 'block_set_position' and 'block_set_params' suggest post-creation workflows this definition never acknowledges.

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% across 6 parameters, so the description must compensate and only partially does. It clarifies 'type' (a catalog type), 'page' (placement target) and 'params' (optional parameter values), and implies x/y are auto-computed via the non-overlapping placement note, but the required 'title' parameter is never mentioned at all.

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 new logic block') and adds scope qualifiers ('of a catalog type', 'to a page'). The parenthetical clarifies placement behavior, so an agent knows this creates rather than modifies. It does not explicitly contrast with sibling 'block_clone', leaving some differentiation to inference.

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 explicit when-to-use guidance, no mention of prerequisites (e.g., discovering a valid type via 'block_addable_types' or 'catalog_list_types'), and no exclusion relative to 'block_clone'. The only implied guidance is the phrase 'of a catalog type', which weakly signals where the type value comes from.

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