Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

blueprint_remove_event_dispatcher

Removes a named event dispatcher from a Blueprint asset, then compiles and saves it. Enables AI coding agents to modify Unreal Engine Blueprints via MCPBridge.

Instructions

Remove an event dispatcher by name, 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>",
      "name": "<name>"
    },
    "name": "blueprint_remove_event_dispatcher"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDispatcher name to remove.
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

A4/5.0
Behavior4/5

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

The description discloses the side-effect that the tool will compile and save after removal, which is valuable information. Since there are no annotations, this description carries the full burden and does well by mentioning the post-removal actions, though it does not cover error cases or prerequisites.

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, front-loaded sentence that clearly states the primary action and the important side-effect. It contains zero wasted words and is appropriately concise for a simple tool.

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

Completeness4/5

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

Given the low complexity (two well-documented parameters, no output schema), the description is essentially complete. It states the operation and subsequent actions, and the schema fills in parameter details. A minor gap is not addressing the 'dispatcher not found' case, but this is not critical for a tool of this simplicity.

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

Parameters3/5

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

Both parameters are fully described in the input schema, and the description only reinforces the 'name' parameter by saying 'by name'. It does not add additional semantic detail beyond the schema, which is acceptable given the high schema coverage.

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 tool removes an event dispatcher by name, which is a specific action on a specific resource. The verb 'remove' and the target 'event dispatcher' distinguish it from sibling tools like blueprint_remove_variable or blueprint_remove_function.

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 description implies usage (when you need to remove an event dispatcher from a Blueprint) but does not explicitly compare with alternatives or state when not to use it. There is no mentioning of exclusions or related tools, leaving room for inference.

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