Skip to main content
Glama

structure_reassign

Move all assignments from a source room or category to a target room or category to reorganize Loxone Gen 1 project structure.

Instructions

Moves all assignments from one room/category to another.

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": {
      "kind": "<kind>",
      "source": "<source>",
      "target": "<target>"
    },
    "name": "structure_reassign"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
sourceYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.7/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. It implies a bulk mutation ('all assignments') but says nothing about permissions, reversibility, what happens to assignments already at the target, or whether the source is emptied.

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 or redundancy. Its brevity is appropriate, though the compact phrasing leaves 'assignments' and 'kind' ambiguous.

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 three undocumented required parameters, no annotations, and no output schema, the description is far too thin. It does not give an agent enough to call the tool correctly or predict its effects.

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 explain all three required parameters. It loosely maps 'source' and 'target' to 'from one room/category to another' but never defines the 'kind' parameter or the expected value formats for any parameter.

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 all assignments') and names the direction of the move ('from one room/category to another'). An agent can tell it is a bulk reassignment operation, though the description never contrasts it with siblings such as structure_remove or structure_list.

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 or when-not-to-use guidance and no alternative tool is named. An agent must infer from the name alone that this is the tool for relocating assignments rather than removing or listing them.

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