Skip to main content
Glama
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403

fgui_import_sound

Import a sound asset into a FairyGUI package from an absolute local path; replace same-name resources and verify package entries after saving.

Instructions

从绝对本地路径导入声音资源;支持替换同名声音,属于磁盘写入。

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>",
      "source_path": "<source_path>"
    },
    "name": "fgui_import_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNo
branchNo
verifyNo
exportedNo
folder_pathNo
source_pathYes
package_nameYes
resource_nameNo
create_foldersNo
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

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden well: it explicitly declares this is a disk write, explains that save=True persists the package/project and then verifies against package.xml (or package_branch.xml for branch writes), and documents the external_reload side effect of unloading and reloading the asset with a reload/disk/none strength in the response. Gaps remain for permissions, timeout behavior, and folder auto-creation, so it is not exhaustive.

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?

Purpose and the disk-write warning are front-loaded, and the second sentence is dense but every clause (package vs branch XML, reload precondition, strength values) adds decision-relevant information. It is somewhat run-on and could be split into bullets, but there is no filler.

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?

For a 12-parameter mutating import with no annotations, the description covers the hardest interactions (save/verify/external_reload and the branch artifact) and correctly references the response field, so an output schema means return values need no further detail. It is still incomplete for the many undocumented parameters and lacks any mention of permissions or failure modes.

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 12 parameters, so the description must compensate and largely does not. It explains save, external_reload, and the verify/strength outcome, and hints that source_path is an absolute local path, but branch, package_name, resource_name, folder_path, exported, create_folders, conflict_policy (with its error/auto_rename/replace enum), and timeout_seconds get no explanation anywhere.

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?

The description states a specific verb and resource (import a sound asset from an absolute local path) and adds the replace-same-name capability, which cleanly separates it from the sibling import tools fgui_import_image and fgui_import_font. An agent knows exactly what the tool does without opening the schema.

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?

It implies usage (absolute local path required, same-name sounds can be replaced) and explains the save/external_reload trigger conditions, including that external_reload requires save=True. However, it never says when to prefer this over alternatives such as fgui_replace_object_resource or fgui_import_image, and gives no guidance on choosing a conflict_policy value.

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