Skip to main content
Glama
Sign In
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

fgui_duplicate_transition

Duplicates a FairyGUI transition with all keyframes, optionally renames and saves it, and verifies the copied transition node in disk XML.

Instructions

复制一个 Transition（含全部关键帧）；可由 fgui_undo 回退。

6.1.4 的 DuplicateTransition 运行时不接受新名称参数，Bridge 会复制后再经文档模型改名； structureNormalized=true 表示副本结构经编辑器归一化，与源不完全一致。省略 new_name 时沿用编辑器自动命名。 save=True 保存后默认比对磁盘 XML 中副本的 节点；external_reload=True（需 save=True）关闭重开再比对。

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": {
      "name": "<name>"
    },
    "name": "fgui_duplicate_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
saveNo
verifyNo
new_nameNo
external_reloadNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.25

TDQS

A4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well: it discloses the version-specific runtime limitation (6.1.4 doesn't accept a new name, so Bridge copies then renames via the document model), explains structureNormalized output semantics, notes the undo path, and clarifies save/verify/external_reload behavior. This is materially more than the annotations or schema convey.

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?

The purpose is front-loaded in the first clause, and each following sentence adds real value rather than filler. Sentences are dense and some run long with nested version-specific details, but nothing is redundant.

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

Completeness4/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 values needn't be explained, and the description covers the key behavioral quirks (version handling, normalization, save/reload verification) well. It stops short of defining the required name parameter and verify semantics, which is a modest gap for a 5-parameter mutation tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for most parameters: new_name (omitted → editor auto-naming), save (save=True → compares disk XML <transition> node), and external_reload (requires save=True, closes and reopens before comparison). The required name parameter and the exact role of verify are not explained, leaving a partial gap.

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 states a specific verb and resource: "复制一个 Transition（含全部关键帧）", which is unambiguous about what is duplicated. It does not directly contrast with siblings like fgui_upsert_transition or fgui_duplicate_object, so the differentiation is implicit rather than explicit.

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 by the act of duplicating an existing transition, and the description notes it can be reverted via fgui_undo. However, it gives no explicit when-to-use guidance versus creating a new transition or using fgui_upsert_transition, so the agent must infer the selection criteria.

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