Skip to main content
Glama

periphery_remove

Deletes an unused virtual input/output, empty virtual output, constant, or weather server from a Loxone Config project; refuses if the object is still used and removes its permission entries.

Instructions

Deletes an unused virtual input/output, an empty virtual output, a constant or the weather server. Refuses while the object is still used anywhere; permission entries are removed with it.

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

Input Schema

NameRequiredDescriptionDefault
blockYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose two important traits: a usage-based precondition that blocks the operation, and a cascade side effect ('permission entries are removed with it'). It does not state irreversibility, required permissions, or what an error/result looks like, which for a destructive tool leaves a gap.

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 tight sentences: the target list comes first and the precondition plus side effect follow. No filler, no restating of the tool name.

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?

Behavior is reasonably covered for a destructive operation with no annotations and no output schema, especially the refusal rule and cascade delete. However, the sole parameter is entirely unexplained and the irreversible nature of the deletion is not stated, leaving the definition incomplete for the risk involved.

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% and the single required parameter 'block' is never mentioned in the description. The agent gets no meaning for what 'block' accepts (a reference, name, or path) or how it identifies the periphery object being removed, so the description fails to compensate for the undocumented schema.

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 names a specific verb ('Deletes') and enumerates the exact target object classes: virtual input/output, empty virtual output, constant, weather server. That enumeration implicitly separates it from block_remove and structure_remove, but it never explicitly states that blocks and structures are removed via other tools, so the differentiation requires inference.

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?

It gives a clear precondition for refusal ('Refuses while the object is still used anywhere'), which tells the agent when this call will fail and must not be attempted. It stops short of naming alternatives such as block_remove or block_disconnect for cases where the object is still in use.

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