Skip to main content
Glama
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403

fgui_create_button

Creates a standard FairyGUI Button component with up/down/over/selected/disabled state images, optional icon and text, and common, check, or radio modes. Saves the package and optionally verifies package.xml.

Instructions

创建标准 FairyGUI Button 组件;状态图顺序为 up/down/over/selectedOver/disabled/selectedDisabled。

save=True 保存包与工程后默认比对 package.xml(分支写入比对 package_branch.xml)条目;组件类资源不支持 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>",
      "button_name": "<button_name>"
    },
    "name": "fgui_create_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocommon
saveNo
widthNo
branchNo
heightNo
verifyNo
exportedNo
image_urlsNo
auto_renameNo
button_nameYes
create_iconNo
create_textNo
folder_pathNo
as_list_itemNo
extension_idNo
package_nameYes
create_foldersNo
create_relationsNo
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.2/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 burden, and it does disclose real behavior: save=True persists the package and project and then compares package.xml entries (package_branch.xml for branch writes), plus a constraint that component-class resources do not support external_reload with strength capped at disk. It remains silent on important mutation traits such as what happens when a button with the same name already exists (auto_rename hints at collision handling) and what verify actually checks.

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 compact sentences with no filler, and the core purpose leads. The emphasis is skewed toward save/verify internals rather than the parameters an agent must actually choose, but nothing is redundant or bloated.

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

Completeness3/5

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

The output schema means return values need not be described, but for a 19-parameter creation tool with zero annotation and zero schema-description coverage, the definition leaves most of the decision surface undocumented. The save/compare behavior is a helpful extra, yet the tool is not fully specified for correct invocation.

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 0% across 19 parameters, so the description must compensate and only partly does: the state ordering maps usefully onto the image_urls array, and save/branch semantics are clarified. However, the important mode enum (common/check/radio), width/height, create_text/create_icon, as_list_item, extension_id, folder_path, auto_rename, exported, and open_after_create 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?

States a specific verb and resource: creates a standard FairyGUI Button component, and adds the non-obvious detail of the state image order (up/down/over/selectedOver/disabled/selectedDisabled). It does not distinguish itself from nearby siblings such as fgui_create_component or fgui_create_movieclip, so an agent cannot tell from the text alone which creation tool to pick.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of prerequisites such as selecting a project or package first, even though siblings like fgui_use_project and fgui_list_packages exist. The only conditional content concerns save/compare behavior, which is not usage routing.

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