Skip to main content
Glama
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403

fgui_list_items

Lists resources in a specified FairyGUI package, with optional filtering by resource type and branch, so agents can inspect available assets without switching branches.

Instructions

列出指定包中的资源,可按 FairyGUI 资源类型过滤。

省略 branch 时跟随当前活跃分支,branch="" 表示主干。返回的分支视角中, 分支资源覆盖同名主干资源;只读操作可以读取非活跃分支,不需要先切换。

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

Input Schema

NameRequiredDescriptionDefault
branchNo
item_typeNo
package_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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. First observedv0.6.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses branch resolution behavior, the branch-overrides-trunk semantics in the returned view, and that read-only reads of non-active branches do not require switching. This is meaningful behavioral context beyond a bare purpose statement.

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 sentence, followed by branch-scoping details. Dense but largely earns its place; the branch paragraph is the longest element but carries useful semantics.

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 simple list tool the description covers purpose, filtering, branch resolution and override behavior adequately. Minor gap is the lack of item_type value hints, but overall it is complete enough to invoke correctly.

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 coverage is 0% with no field descriptions, so the description must compensate. It explains the branch parameter thoroughly and implies package_name (specified package) and item_type (filter by resource type), but it does not enumerate valid item_type values or give format details, leaving some ambiguity.

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: lists resources in a specified package, with optional filtering by FairyGUI resource type. It is clearly distinct from fgui_list_packages (lists packages) and fgui_get_list_items (list component contents). It does not explicitly name a sibling it is not, so it falls just 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?

The branch explanation (omitting branch follows the active branch, branch="" means trunk) gives real usage context for one parameter. However, there is no explicit guidance on when to choose this tool versus alternatives like fgui_get_tree or fgui_query_dependencies; usage is implied rather than stated.

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