Skip to main content
Glama

unreal_remove_widget

Removes a widget from an Unreal Engine project, deleting the specified UI widget to clean up or update in-editor interfaces.

Instructions

Remove a widget.

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_remove_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden for a destructive mutation, yet it discloses nothing: not whether removal is reversible, whether child widgets are removed with it, whether a save/recompile step is required, or what errors occur if the widget is absent. The single sentence adds no information beyond the tool name.

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

Conciseness2/5

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

Three words is technically concise, but here brevity reflects under-specification rather than efficiency; there is no structure, no front-loaded context, and nothing that earns the sentence's place beyond restating the tool name.

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?

For a destructive mutation tool with zero annotations and a completely undescribed parameter object, the definition is inadequate. The output schema exists, so return values need not be explained, but the agent cannot reliably determine what argument to pass or what the removal affects.

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 one required parameter named "params" with 0% schema description coverage and no defined properties, and the description offers no explanation of what must be passed (widget name, path, id?). The description does nothing to compensate for the opaque schema.

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?

"Remove a widget" states a specific verb and resource, so the basic operation is inferable. However, it gives no scope: which widget, in what context (widget blueprint vs. viewport), and it doesn't distinguish itself from nearby siblings such as unreal_remove_component or unreal_remove_blueprint_variable.

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 at all — no preconditions (widget must exist, must be in the tree), no alternatives, no mention of what to use instead for removing components or blueprint variables. The agent must infer everything from 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