Skip to main content
Glama
Sign In
UE5-MCP-Server

UE5-MCP-Server

by hahatu112113
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ue5_save_asset

Save an Unreal Engine 5 asset by specifying its asset path, persisting changes made through AI-driven scene or code modifications.

Instructions

Saves a specific 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": {
      "assetPath": "<assetPath>"
    },
    "name": "ue5_save_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetPathYesThe asset path to save.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only says 'saves' without indicating whether it overwrites, requires the asset to be loaded, or any side effects. This is insufficient for safe tool use.

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

Conciseness4/5

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

The description is a single sentence, concise and front-loaded. However, it sacrifices substance for brevity, lacking important details.

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?

Given the absence of annotations and output schema, the description should provide more context. It does not explain what 'saves' entails (e.g., to disk, immediate effect) or differentiate from 'ue5_save_level'. The tool is simple but still incomplete for an agent to use confidently.

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?

The input schema covers the single parameter 'assetPath' with a description. The tool description adds no further meaning beyond the schema, so with 100% schema coverage, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Saves a specific asset,' which is a verb+resource clearly indicating the action. However, it does not differentiate from sibling tools like 'ue5_save_level' which also save, making the purpose less distinct.

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?

No usage guidelines are provided. The description does not specify when to use this tool over alternatives like 'ue5_save_level' or 'ue5_duplicate_asset', nor does it mention prerequisites or context.

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