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

fgui-agent-bridge

by Wilson520403
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

fgui_set_keyframe

Modify an existing FairyGUI keyframe by index or target/track/frame to update timing, label, tween, easing, repeat, yoyo, or values; optionally save and verify.

Instructions

修改一个已有关键帧；可用 item_index，或 target_id + track_type + frame 定位。

按 target_id/type/frame 还能定位 get_transition 隐藏的 Tween 合成端点（此时 itemIndex=null、syntheticEndpoint=true）。changes 支持 frame / label / tween / ease / repeat / yoyo / value / endValue。tween=true 只能用于已处于 Tween 关系中的关键帧 （Tween 起点，或插入已有 Tween 后形成的端点）；普通关键帧之间建立 Tween 请用 fgui_upsert_transition。endValue 写入 Tween 端点；tween=false 不能同时给 endValue。 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>",
      "changes": "<changes>"
    },
    "name": "fgui_set_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
saveNo
frameNo
verifyNo
changesYes
target_idNo
item_indexNo
track_typeNo
external_reloadNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.25

TDQS

A4.5/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 disclose real side effects: save=True writes to disk and by default diffs against the on-disk XML, and external_reload=True forces a close/reopen before comparing. It does not describe error behavior when a keyframe fails to resolve or whether changes are atomic, so it falls slightly short of complete behavioral disclosure.

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?

Front-loaded with purpose, then addressing, then the changes payload, then save/verify mechanics — a logical order with no filler sentences. It is dense and terminology-heavy, but every clause conveys a constraint an agent would otherwise get wrong.

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 need not be explained. For a 9-parameter mutation tool with zero annotation coverage, the description covers locating, the mutable field set, Tween constraints, and save/verify semantics. Only edge-case failure behavior and the meaning of 'name' remain unstated.

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 description coverage is 0%, so the description must compensate and largely does: it explains the two locator strategies, enumerates the changes fields (frame/label/tween/ease/repeat/yoyo/value/endValue), and states the mutual exclusion that tween=false cannot be combined with endValue. The 'verify' and 'name' parameters are only implicitly covered, leaving a small gap.

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?

States a specific verb+resource ("修改一个已有关键帧" / modify an existing keyframe) and immediately gives the two supported addressing schemes (item_index vs target_id + track_type + frame). It also distinguishes itself from the sibling fgui_upsert_transition by name, so an agent can pick the right tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: creating a Tween between ordinary keyframes must go to fgui_upsert_transition, while tween=true here only applies to keyframes already in a Tween relation. It also states the synthetic-endpoint case and the external_reload-requires-save precondition, covering both when-to-use and when-not.

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