ue_duplicate_asset
Duplicate an asset to create a modifiable variant quickly.
Instructions
Duplica un asset: la via rapida per crearne una variante da modificare.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| new_path | Yes |
Duplicate an asset to create a modifiable variant quickly.
Duplica un asset: la via rapida per crearne una variante da modificare.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| new_path | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It only states 'duplicate' but does not disclose side effects (e.g., dependency copying, asset loading requirements, overwrite behavior). The context of creating a 'variant' implies modification, but details are lacking.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (one sentence) and front-loaded with the core action. However, it is too minimal for the tool's needs, missing parameter details. It earns points for being concise but loses for under-specification.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 required string params, no output schema), the description is incomplete. It does not explain the path semantics, whether it creates a new asset or replaces an existing one, or any prerequisites like asset must be loaded.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description provides no explanation of the two parameters ('path', 'new_path'). No information on format (absolute, relative, content browser paths) or expected values, leaving the agent with no guidance beyond the schema names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool duplicates an asset to create a variant for modification, using a specific verb ('duplica') and resource ('asset'). It distinguishes from sibling tools like ue_delete_asset or ue_rename_asset by focusing on duplication.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The phrase 'la via rapida' hints at a faster method but does not specify when not to use it or mention any alternative duplication methods.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Groggy-rollcall812/unreal-engine-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server