Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

duplicate_mpc

Copy an Unreal Engine Material Parameter Collection asset, including parameter names, IDs, and defaults, to a new name and folder, then save it. It rejects an existing target path.

Instructions

Duplicate a Material Parameter Collection asset, parameters included with their names, Ids and defaults, to package_path/new_name and save the copy. Refuses when the target already exists. Returns collection_path, scalar_count, vector_count, saved and save_error.

Returns: { source_path: string, collection_path: string, asset_path: string, name: string, package_path: string, scalar_count: int, vector_count: int, duplicated: bool, saved: bool, save_error: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_nameYesAsset name of the copy, e.g. "MPC_B"; must not be empty
source_pathYesSource MPC path, e.g. "/Game/MPC/MPC_A" or the object path "/Game/MPC/MPC_A.MPC_A"
package_pathNoTarget folder; default is the folder of source_path when it is an object path with a dot ("/Game/MPC/MPC_A.MPC_A"), else "/Game/MaterialCollections"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / new_name / description
      Previous value: -"Name for the duplicated MPC"New value: +"Asset name of the copy, e.g. \"MPC_B\"; must not be empty"
    • changedInput schema / properties / package_path / description
      Previous value: -"Target package path, defaults to source's folder"New value: +"Target folder; default is the folder of source_path when it is an object path with a dot (\"/Game/MPC/MPC_A.MPC_A\"), else \"/Game/MaterialCollections\""
    • changedInput schema / properties / source_path / description
      Previous value: -"Full /Game path of the source MPC"New value: +"Source MPC path, e.g. \"/Game/MPC/MPC_A\" or the object path \"/Game/MPC/MPC_A.MPC_A\""
  2. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare a non-readOnly, non-idempotent, non-destructive write; the description adds real context beyond that: parameters and their Ids/defaults are preserved, the copy is saved, and the operation refuses when the target exists, with explicit saved/save_error reporting.

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?

Front-loads the core action, then the refusal constraint. The trailing return-value listing is a bit long but justified because no output schema exists, so it is not redundant.

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

Completeness5/5

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

With no output schema, the description supplies the return shape (collection_path, counts, saved, save_error), plus the destination, refusal behavior and asset-copy specifics. An agent has everything needed to call it correctly.

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?

Schema description coverage is 100%, so the schema already documents how source_path and package_path are interpreted, including the object-path-vs-folder default logic. The description restates package_path/new_name composition but adds no syntax beyond the schema, so the baseline 3 applies.

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?

Specific verb (Duplicate) plus a precisely named resource (Material Parameter Collection asset) and scope: parameters carried with names, Ids and defaults. The destination (package_path/new_name) and save behavior are stated, letting an agent distinguish this from generic duplicate_asset.

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 states the refusal condition when the target already exists, which is useful context, but gives no explicit when-to-use guidance or comparison to alternatives like duplicate_asset. Usage must be inferred.

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