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

fgui-agent-bridge

by Wilson520403
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

fgui_query_dependencies

Query which FairyGUI resources a target resource depends on, with configurable seek scope. Read-only; reports the effective seek level and supports item limits.

Instructions

查询目标资源依赖了哪些资源（只读，0.8.10+）。

走编辑器原生 DependencyQuery。seek_level 取 selection / samePackageButNotExported / samePackage（默认）/ all，决定依赖搜索范围；响应会回报实际生效的 seekLevel。

只读：不会保存、不会标记文档修改。max_items、skip_package_open 同 fgui_query_references。

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

Input Schema

NameRequiredDescriptionDefault
max_itemsNo
seek_levelNosamePackage
resource_urlYes
skip_package_openNo

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, the description carries the full burden and does disclose key traits: it is read-only, will not save, will not mark the document modified, and requires editor 0.8.10+. It also notes the response echoes the effective seekLevel. It stops short of saying what happens on truncation or whether unopened packages are queried by default.

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 description is front-loaded with the purpose and then builds out scope and safety in short lines, with little waste. The 'same as fgui_query_references' shortcut is compact but shifts real information outside this definition.

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, and the read-only guarantees plus scope enumeration give an agent enough to invoke it correctly. The only shortfall is the two delegated parameters, which a caller may still need to resolve elsewhere.

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%, so the description must compensate. It does this well for seek_level, listing all values and the default and noting the effective value is reported back, but it only hand-waves max_items and skip_package_open by pointing at fgui_query_references, so an agent still cannot tell what max_items limits or what skip_package_open suppresses without opening another tool.

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 first line states a specific verb and resource: which resources the target resource depends on, with a version qualifier (0.8.10+). It is distinguishable from the sibling reference-query tool by direction (dependencies vs. references), but the description never explicitly contrasts the two, leaving that inference to the reader.

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 seek_level enumeration (selection / samePackageButNotExported / samePackage / all) gives the agent a usable notion of scope, and the read-only note clarifies the side effect. There is no explicit 'when to use this instead of fgui_query_references or fgui_find_unused' routing guidance, so 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