Skip to main content
Glama
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403

fgui_create_component

Creates a new FairyGUI component document in a specified package, opening it without saving by default and rejecting duplicate names.

Instructions

在指定包中新建组件文档;默认打开但不保存,重名时默认拒绝。

save=True 保存包与工程后默认比对 package.xml(分支写入比对 package_branch.xml)条目;组件类资源没有可靠的 asset 重载手段,external_reload 不可用,strength 上限为 disk。

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>",
      "component_name": "<component_name>"
    },
    "name": "fgui_create_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNo
widthNo
branchNo
heightNo
verifyNo
exportedNo
auto_renameNo
folder_pathNo
extension_idNo
package_nameYes
component_nameYes
create_foldersNo
open_after_createNo

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. Changed2 schema fields changedv0.8.6
    • addedInput schema / properties / save
      Added value: +{
      +  "default": false,
      +  "title": "Save",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / verify
      Added value: +{
      +  "default": true,
      +  "title": "Verify",
      +  "type": "boolean"
      +}
  3. First observedv0.6.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose real traits: the mutation is non-persistent by default, duplicate names are refused, save=True triggers package.xml comparison (package_branch.xml on branches), and component resources cannot be externally reloaded so strength caps at disk. It still omits whether creation is undoable, what permissions/project context are needed, and side effects on the currently open document.

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

Conciseness3/5

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

The action and its defaults are front-loaded, which is good, but the second paragraph is dense jargon (package.xml/package_branch.xml, external_reload, strength=disk) whose connection to 'create a component' is not explained. It is short for 13 parameters, but the density trades clarity for brevity.

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 13-parameter mutation tool with no annotations and zero schema descriptions, the definition leaves most parameters and the broader creation semantics undocumented, even though an output schema does relieve it of explaining return values. An agent could call it with the two required args but could not reason about the other eleven.

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 13 parameters, so the description must compensate and largely does not. It only implicitly touches save, auto_rename (via the duplicate-name default), open_after_create (via 'opened by default') and branch; width, height, folder_path, create_folders, extension_id, exported and verify are left completely unexplained.

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 first clause names a specific verb and resource (create a component document inside a named package) and adds concrete defaults: opened but not saved, duplicate names rejected. It does not distinguish this from nearby siblings such as fgui_create_button, fgui_create_movieclip or fgui_create_group, so an agent must infer which creator applies from names alone.

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?

Usage is implied rather than stated: the description tells you the default outcome (opens unsaved, rejects duplicates) which hints at when you'd want save=True or auto_rename, but it never says when to use this tool versus the other create_* tools or what prerequisites (active project, valid package) are required.

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