Skip to main content
Glama

ref_add

Adds an input or output reference placeholder for a block or peripheral on a Loxone page so the connector can be wired there.

Instructions

Adds a placeholder (input or output reference) for a block or peripheral object to a page, so it can be wired there.

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

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
kindNo
pageYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/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 disclosure burden. It states that the tool adds a placeholder, but omits permissions, duplicate handling, persistence, reversibility, and side effects on the page.

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?

The description is a single, front-loaded sentence with no filler, and the purpose clause adds useful context. It is appropriately sized and structured for a concise tool definition.

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 five-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the one-sentence description is inadequate. It leaves parameter formats, validation rules, and failure behavior unexplained.

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 description only indirectly identifies page as the destination and target as the block or peripheral object. It says nothing about x, y, or kind, leaving three of five parameters undocumented in both schema and description.

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 uses a specific verb ('Adds') and defines the resource precisely: a placeholder input/output reference for a block or peripheral on a page. It also conveys the intent ('so it can be wired there'), though it does not explicitly distinguish itself from block_add or page_add.

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?

The clause 'so it can be wired there' implies this is a setup step performed before wiring, giving some context for use. However, there is no explicit when/when-not guidance, prerequisites, or named alternative tool.

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