Skip to main content
Glama

unreal_disconnect_blueprint_nodes

Disconnect Blueprint node pins in Unreal Engine to remove unwanted links and correct logic flow.

Instructions

Disconnect 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_disconnect_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.1/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 burden and discloses almost nothing. It does not say whether disconnecting is reversible, whether it affects compiled graphs or dependent nodes, what happens if a pin is not connected, or whether an editor session is required.

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?

The single sentence is front-loaded and free of waste, but brevity here reflects under-specification rather than disciplined editing. Nothing in it is unnecessary, yet little of it is useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a mutation with no annotations, an opaque untyped params object, and no explanation of side effects. Although an output schema exists and return values need not be described, an agent still cannot construct a correct call from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter whose schema is an untyped "Params" object with 0% description coverage, and the description says nothing about its shape or contents. The agent has no way to learn what identifying information (node name, pin name, graph) to supply.

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

Purpose3/5

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

"Disconnect Blueprint node pins" names a specific verb and resource, so the agent can tell it apart from unreal_connect_blueprint_nodes. However, it is ambiguous about whether the unit of work is the node or the pin, and it never states how pins are identified, leaving the actual operation vague.

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 guidance, no prerequisites (e.g., whether the Blueprint must be open or selected first), and no mention of a condition that would select it over connect_blueprint_nodes or disconnect_material_nodes. Usage is only implied by the verb in the name.

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