BlockWerk

Connect blocks

connect_blocks

Connect an output port of one block to an input port of another. Automatically resolves common port aliases (e.g., "in" -> "signal" for uPlotDisplay, "in" -> "error" for PIDController, "+" / "-" for Subtraction).

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": {
      "fromBlockId": "<fromBlockId>",
      "fromPortId": "<fromPortId>",
      "toBlockId": "<toBlockId>",
      "toPortId": "<toPortId>"
    },
    "name": "connect_blocks"
  }
}

Input Schema

Name	Required	Description
`toPortId`	Yes	Input port ID of the destination block, e.g. "in" (aliases like "signal" or PID "error" are supported)
`toBlockId`	Yes	ID of the destination block
`fromPortId`	Yes	Output port ID of the source block, e.g. "out" (aliases like "signal", "y" are supported)
`fromBlockId`	Yes	ID of the source block

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context about automatic alias resolution, but omits important semantics: whether connecting to an already-occupied input port overwrites the existing edge, and what happens on invalid port or block IDs.

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 sentences, zero filler, and the core action is front-loaded before the alias-resolution detail. Every clause earns its place.

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?

All four required parameters are fully documented and annotations carry the safety profile, but for a graph-mutation tool the description never states overwrite behavior on occupied input ports, failure modes for invalid IDs, or whether the response confirms the new edge. These gaps matter for correct invocation sequencing.

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 coverage is 100% and the schema already mentions alias support, so the baseline is 3. The description goes further by giving block-specific alias mappings ("in" -> "signal" for uPlotDisplay, "in" -> "error" for PIDController, "+"/"-" for Subtraction), which is concrete meaning an agent could not derive from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise verb and resource with directionality: connect an output port of one block to an input port of another. This is clearly distinguishable from siblings like add_block (creates) and delete_block (removes), so an agent can select it without ambiguity.

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, no prerequisites (both blocks must already exist), and no mention of alternatives such as add_block for creating the blocks first. Usage is only weakly implied by the verb.

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

All BlockWerk tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?