Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

blueprint_node_set_enabled

Enable or disable a Blueprint node by GUID, then compile and save. Solves manual editing tasks in Unreal Engine blueprint graphs.

Instructions

Enable or disable a node by GUID, then compile and save.

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": {
      "blueprint_path": "<blueprint_path>",
      "graph_name": "<graph_name>",
      "node_guid": "<node_guid>",
      "enabled": "<enabled>"
    },
    "name": "blueprint_node_set_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
node_guidYes
graph_nameYes
blueprint_pathYesContent path of the Blueprint asset, e.g. /Game/Blueprints/BP_Door.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description must disclose behavioral traits. It explicitly mentions the significant side effects of compiling and saving, which is helpful for a mutation tool. However, it omits error behavior, permissions, and reversibility.

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 concise sentence with no filler. It front-loads the core action and every word contributes to understanding the operation.

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?

Given the lack of annotations and output schema, the description is sparse. It covers the main action and side effects but does not explain graph_name usage or potential errors, leaving it minimally complete for a 4-parameter tool.

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?

The schema only describes blueprint_path (25% coverage). The description adds minimal semantics by referencing GUID for node_guid and enable/disable for the enabled boolean, but graph_name remains unexplained and other parameter details are absent.

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 clearly states the action (enable/disable), target (a node by GUID), and side effects (compile and save). It is specific and distinguishes from sibling tools like blueprint_node_add and blueprint_node_delete.

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 purpose implies the tool is for toggling a node's enabled state, but it provides no explicit when-to-use or alternative guidance. It lacks exclusions or references to related tools.

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