Skip to main content
Glama

block_connect

Connect an output of one block to an input of another on the same page to link blocks in Loxone Config projects.

Instructions

Connects an output of one block to an input of another on the same page.

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": {
      "from_block": "<from_block>",
      "to_block": "<to_block>"
    },
    "name": "block_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
to_blockYes
from_blockYes
to_connectorNo
from_connectorNo

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 conveys that this is a mutation and that it is page-scoped, but says nothing about what happens if the connection already exists, whether it overwrites or errors, permission requirements, or what the response contains.

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 tight sentence with the core action front-loaded and zero filler. It is under-specified rather than verbose, which is the better failure mode, but the brevity costs needed detail.

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?

Five parameters, no annotations, no output schema, and no parameter documentation — the one-line description is not enough for an agent to invoke this correctly without guessing at connector and page semantics.

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% across five parameters. The description only implicitly maps to from_block and to_block; it says nothing about from_connector and to_connector (which output/input port to target) or about the page parameter's role and default. For a 5-param tool with no schema docs, this leaves real ambiguity.

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?

States a specific verb and resource: connects an output of one block to an input of another. The 'on the same page' scope is a useful disambiguator. It does not explicitly name block_disconnect as the inverse operation, so sibling differentiation is only implied.

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?

No guidance on when to use this versus block_disconnect, block_add, or block_clone, and no prerequisites stated (e.g. blocks must exist, connectors must be compatible). The same-page constraint is the only usage-relevant hint.

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