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

fgui-agent-bridge

by Wilson520403
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

fgui_insert_list

Creates a List under the current FairyGUI document root component with configurable layout, default item component, and initial items; optionally saves and verifies the result.

Instructions

在当前文档根组件下创建 List，支持布局、默认条目组件和初始条目（0.8.25+）。

default_item 与条目 url 必须引用组件；每项省略 url 时使用 default_item。 items 最多 1000 项，可写 url/title/icon/name/selectedTitle/selectedIcon，图标须引用图片。 x/y/width/height 向零截断，尺寸须大于 0；间距须为整数。 支持保存、XML 条目回读与关闭重开验证。不进 Agent 撤销栈，未保存可 discard。 save 保存整个文档；external_reload 要求 save=true 且 verify=true。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fgui_insert_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNo
saveNo
alignNoleft
itemsNo
widthNo
heightNo
layoutNosingle_column
verifyNo
v_alignNotop
line_gapNo
overflowNoscroll
column_gapNo
default_itemNo
auto_item_sizeNo
selection_modeNosingle
external_reloadNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.25

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 full burden and does well: it discloses that the operation does not enter the Agent undo stack, that unsaved changes can be discarded, that save persists the entire document, and that verification reads items back via XML and close/reopen. It omits error conditions and any prerequisites such as an open document, keeping it short of a 5.

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 sentence is front-loaded and the following sentences are dense constraint clauses with little filler. Some rules (truncation, gap integers) are terse to the point of being fragmentary but each still carries information.

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?

For an 18-parameter mutation tool with no annotations, the description covers the highest-risk semantics (undo, save scope, verification, resource reference rules, caps) and an output schema exists so return values need not be explained. Remaining gaps are the unaddressed layout/alignment/selection parameters.

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 18 parameters, so the description must compensate. It adds real meaning for default_item, items (field set, 1000-item cap, icon-must-reference-image rule), x/y/width/height truncation and size bounds, and save/external_reload/verify interplay, but leaves layout, align, v_align, overflow, selection_mode, auto_item_size, and name entirely to the bare enum/default schema.

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 opens with a specific verb+resource: create a List under the current document's root component, and names the distinguishing capabilities (layout, default item component, initial items, version 0.8.25+). This clearly separates it from the generic fgui_insert_object without naming it explicitly.

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 gives conditional rules (external_reload requires save=true and verify=true; unsaved content can be discarded) that effectively steer usage, but never states when to pick this over fgui_insert_object or when to modify an existing list via fgui_set_list_items. Guidance is implied through constraints rather than explicit alternatives.

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