Skip to main content
Glama

unreal_connect_blueprint_nodes

Connect two Blueprint node pins to establish logic links between nodes in an Unreal Engine 5 Blueprint graph.

Instructions

Connect two Blueprint node pins.

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": {
      "params": "<params>"
    },
    "name": "unreal_connect_blueprint_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 and delivers almost none. It does not say whether connecting replaces an existing pin connection, whether it requires compilation or save afterwards, whether it fails on incompatible pin types, or whether the change is undoable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero padding, but its brevity comes from omission rather than precision. There is no structure beyond a bare statement of intent.

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 no annotations, an opaque untyped params object, and 0% schema coverage, the description is far too thin. The existence of an output schema means return values need not be explained, but inputs and side effects are entirely undocumented.

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 coverage is 0% and the single parameter is an untyped 'params' object, so the schema explains nothing. The phrase 'two Blueprint node pins' hints that the payload involves a source and target pin, but the description never names the fields, their format, or how pins are identified.

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 ('Connect') and resource ('Blueprint node pins'), which is enough to distinguish it from unreal_disconnect_blueprint_nodes and unreal_connect_material_nodes among the siblings. It stops short of explicitly naming those alternatives, so a 4 rather than a 5.

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 mention of prerequisites such as the graph/blueprint being open, and no pointer to the disconnect counterpart. The agent must infer all usage context from the tool name alone.

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

Deploy Server

Other Tools