Skip to main content
Glama

block_clone

Clones an existing Loxone block with its settings and sub-objects to a page without connections, enabling creation of large blocks that simple addition cannot. Wire and verify after cloning.

Instructions

Adds a copy of an existing block with all settings and sub-objects to a page, without its connections. This also creates large blocks such as lighting controller, room controller or automatic blinds that block_add cannot create. Then wire it (block_connect) and check the settings.

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>",
      "page": "<page>",
      "title": "<title>"
    },
    "name": "block_clone"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
blockYes
titleYes
source_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: what is copied (settings, sub-objects), what is not (connections), and that manual wiring is required afterward. It omits the return value (there is no output schema, so the agent cannot learn whether a new block id comes back), conflict handling on duplicate titles, and whether the operation is atomic if the page is invalid.

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?

Front-loads the core operation, then the distinguishing capability, then the follow-up workflow. Three sentences, no filler; the only nit is the slightly run-on second sentence with three example block types.

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 4-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the description should define title and source_page and say what comes back (new block reference?). It covers the conceptual copy semantics and the wiring workflow well but leaves two required-ish inputs and the result underspecified.

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 description coverage is 0%, so the description must compensate, and it only partially does: 'block' and 'page' are implied by 'copy of an existing block ... to a page', but 'title' (presumably the new block's name) and especially 'source_page' (default null) are never explained. Two of four parameters get no semantic guidance anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 copy of an existing block') and pins the semantics precisely: copies all settings and sub-objects, excludes connections. It also names the sibling it supersedes for specific cases ('large blocks ... that block_add cannot create'), so an agent can distinguish it without opening another schema.

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

Usage Guidelines4/5

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

Gives a clear selection rule against block_add (use this when the block type is a lighting/room controller or automatic blinds, which block_add cannot create) and describes the follow-up workflow (wire with block_connect, then check settings). It stops short of stating explicit when-not conditions or prerequisites such as whether the source block must be on a live page.

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