Skip to main content
Glama

unreal_save_blueprint

Save a Blueprint asset in an Unreal Engine 5 project to persist edits made through the editor bridge, helping prevent unsaved changes from being lost.

Instructions

Save a Blueprint asset.

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

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 supplied, so the description carries the full burden of behavioral disclosure. It conveys only that a write/persistence operation occurs; it does not state whether the save writes to disk immediately, whether it fails on a read-only or unopened asset, whether it triggers compilation, or whether it can overwrite prior state, all of which matter for a mutation tool.

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?

The sentence is short and front-loaded with no wasted words, but this is under-specification rather than conciseness. A single six-word sentence cannot carry the meaning this tool needs.

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?

An output schema exists, so return values need not be explained. But for a mutation tool with no annotations and a completely undocumented nested "params" object, the definition leaves critical gaps: the agent knows neither the target asset nor the argument shape nor the side effects.

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?

The single required parameter is named "params" with a title only and 0% schema description coverage, so its content is entirely opaque. The description adds no information about what the parameter should contain (asset path, name, flags), leaving the agent unable to construct a valid call.

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?

The description gives a concrete verb and resource ("Save a Blueprint asset"), which is better than restating the tool name alone. However, it does not say which Blueprint is saved (the currently open one? one identified by a path/name argument?) and does not distinguish itself from the close siblings unreal_save_asset, unreal_save_blueprint-like variants, or unreal_save_all, so an agent cannot tell which save tool applies without opening the schema.

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 statement of preconditions, no mention of when to prefer unreal_save_all or unreal_save_asset instead, and no note about what happens if the Blueprint has unsaved changes or is not open. The only implied usage is the obvious one 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