Skip to main content
Glama
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403

fgui_create_movieclip

Create or replace a FairyGUI MovieClip using ordered absolute image paths, with controls for frame timing, saving, verification, conflict handling, and asset reload.

Instructions

用有序绝对图片路径创建或替换 MovieClip;图片序列由 FairyGUI 原生动画资源处理。

save=True 保存包与工程后默认比对 package.xml(分支写入比对 package_branch.xml)条目和资源文件;external_reload=True(需 save=True)卸载并重新加载 asset 再比对,响应 strength 为 reload / disk / none。

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": {
      "package_name": "<package_name>",
      "movieclip_name": "<movieclip_name>",
      "frame_paths": "<frame_paths>"
    },
    "name": "fgui_create_movieclip"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
saveNo
swingNo
branchNo
verifyNo
exportedNo
folder_pathNo
frame_pathsYes
frame_delaysNo
package_nameYes
repeat_delayNo
create_foldersNo
movieclip_nameYes
conflict_policyNoerror
external_reloadNo
timeout_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.25
    • addedInput schema / properties / branch
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Branch"
      +}
  2. Addedv0.8.6

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does real work: it discloses that save=True writes the package and project, that verification compares package.xml entries (package_branch.xml on branch writes), that external_reload unloads and reloads the asset, and that the response strength field is one of reload/disk/none. It stops short of describing what 'replace' destroys (existing frames, delays, swing settings) or the cost/timeout behavior.

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?

Two tight paragraphs: purpose and path semantics first, then the save/verify/reload chain. Dense but front-loaded with no filler sentences; the second paragraph could be split for readability but nothing is redundant.

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?

For a 16-parameter mutation tool with zero annotations, the definition leaves most of the surface unexplained — particularly conflict_policy, which governs whether an existing MovieClip is overwritten, and the frame_delays/fps timing model. The output schema relieves it of explaining return values, but an agent still cannot reason about most arguments from this description alone.

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?

Schema description coverage is 0% across 16 parameters, so the description must compensate, and it only explains save and external_reload. Key parameters like conflict_policy (error/auto_rename/replace), frame_delays, swing, repeat_delay, fps, verify, exported, folder_path, create_folders, branch, and timeout_seconds get no semantic elaboration beyond their names and defaults.

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 opens with a specific verb+resource pair: create-or-replace a MovieClip from ordered absolute image paths, with the mechanism (FairyGUI native animation resources) named. It implicitly separates itself from fgui_update_movieclip and fgui_get_movieclip by scope, but never names those siblings explicitly.

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 'create or replace' framing and the conditional 'external_reload requires save=True' note give an agent some decision context, but there is no explicit when-to-use-this-vs-alternatives guidance (e.g. update_movieclip vs create_movieclip), and no prerequisite or prerequisite-failure guidance.

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