Skip to main content
Glama

unreal_save_all

Save all dirty packages in an Unreal Engine 5 project to persist unsaved changes.

Instructions

Save dirty packages.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 behavioral burden, and it discloses only that non-dirty (unmodified) packages are skipped. It says nothing about write side effects, whether unsaved levels or new assets are included, permission requirements, prompts, progress, or whether the operation can be interrupted or undone.

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?

At three words it is not so much concise as under-specified; there is no wasted wording, but the sentence is a fragment that omits the scope information an agent most needs. Brevity here costs clarity rather than buying it.

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 mutation tool with no annotations, an undocumented required parameter, and many save-related siblings, the definition is materially incomplete. The output schema does relieve it of explaining return values, but nothing else about calling it correctly is covered.

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?

There is one required parameter, 'params', with a completely empty schema (0% description coverage, no type), and the description offers no explanation of its shape or expected contents. Because a parameter exists, the zero-parameter baseline of 4 does not apply, and the description does nothing to compensate for the schema gap.

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 fragment 'Save dirty packages' does convey a verb (save) and an object (packages), with the useful qualifier 'dirty' indicating only modified content is written. However it never clarifies scope relative to siblings like unreal_save_asset, unreal_save_level, or unreal_save_blueprint — an agent cannot tell whether this is a bulk save of everything or a narrowly targeted one.

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 conditions selecting this over the many per-asset save siblings, and no preconditions (e.g. whether it should follow edits, or be run before build/capture operations). The 'all' in the name hints at a bulk operation but the description never states it.

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