Skip to main content
Glama

block_set_position

Moves a block or placeholder to specified x/y coordinates on a Loxone page, enabling precise layout rearrangement using Loxone's 96-unit grid.

Instructions

Moves a block or placeholder on its page (x/y in Loxone units, grid 96; the sheet extends to about 23,400 x 16,300).

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>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "block_set_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
pageNo
blockYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/5.0
Behavior3/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 usefully discloses the coordinate system and valid extent (Loxone units, grid 96, ~23,400 x 16,300), which is real behavioral context. But it omits whether the move is immediately persisted or staged pending a save, what happens if coordinates fall outside the grid, and what identifiers are accepted for 'block'.

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?

One sentence with the action front-loaded and the unit/grid details in a compact parenthetical. The sheet-dimension figures are borderline but do establish a valid coordinate range, so 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 mutation tool with no annotations, no output schema, and 0% schema coverage across four parameters, the description explains positioning but not identity or persistence semantics. An agent could call it correctly on the happy path, but critical details such as what 'block' expects and whether changes require a save remain unstated.

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

Parameters4/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. It does so well for x and y (units, grid snapping, page bounds), which is the core of the operation. It adds nothing for 'block' (ID vs. name) or for the optional 'page' parameter's default of null/current page, leaving a gap despite strong coverage of the coordinate pair.

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?

The description states a specific verb and resource ('Moves a block or placeholder on its page'), which clearly separates it from siblings like block_set_params or block_set_inverted. It does not explicitly name a sibling to contrast with, but the operation is unambiguous.

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?

Usage is implied: an agent reading 'moves a block or placeholder on its page' knows this is the positioning tool. However, there is no statement of when to use it versus alternatives, no mention of prerequisites (does the block need to exist? must the page be current?), and no note about interaction with the project_changes/discard staging siblings.

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