Skip to main content
Glama
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403

fgui_import_font

Imports a font from an absolute local path into a FairyGUI package, writing it to disk and resolving same-name conflicts via reject, auto-rename, or replace.

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_font"
  }
}

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

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares this is a disk write, explains what replace does to a same-named font, and describes the save→verify pipeline including branch-specific package_branch.xml comparison and the reload/disk/none strength values. It still omits permission requirements and failure/partial-write behavior for a 12-parameter mutation.

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?

Purpose is front-loaded in the first clause, which is good, but the second sentence is a dense run-on with nested parentheticals and semicolons that is hard to parse in one pass.

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?

An output schema exists, so return shape needn't be spelled out, and the description does explain the strength field. For a 12-parameter write operation with zero annotation coverage, though, half the parameters and the failure semantics remain undisclosed, leaving the definition only partially complete.

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 it only meaningfully explains conflict_policy, save, and external_reload (plus the absolute-path nature of source_path). verify, exported, folder_path, resource_name, create_folders, branch, and timeout_seconds are left entirely opaque to the agent.

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+resource ('import font') plus the origin constraint ('absolute local path'), so the agent can distinguish it from fgui_import_image and fgui_import_sound by resource type. It does not explicitly name those siblings, so it stops short of a 5.

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?

Gives useful conditional prerequisites, notably that external_reload requires save=True, and enumerates the three conflict behaviors. However it never says when to choose this tool over the other import/publish siblings, so usage is implied rather than routed.

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