Skip to main content
Glama
fgui-agent-bridge

fgui-agent-bridge

by Wilson520403

fgui_get_tree

Reads the current component object tree to retrieve stable object IDs or paths needed before making edits, optionally checking that the active document belongs to a specified branch.

Instructions

读取当前组件对象树;修改前应先取得稳定的对象 ID 或路径。

branch 指定时要求当前文档属于该分支;只读读取不要求该分支处于活跃状态。

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_get_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNo
max_depthNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full disclosure burden and does note that the operation is a read-only read (只读读取) and that it does not require the branch to be active. It also discloses the branch-membership precondition, which is a real behavioral constraint. It does not describe the shape or size of the returned tree, though an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded statements: purpose plus workflow guidance first, then the branch constraint. Every clause carries information and nothing is repeated from the schema or title.

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 a read-only tree tool with an output schema, the description covers purpose, read-only nature, and the branch precondition well. The only meaningful omission is any guidance on max_depth and the cost of a deep traversal.

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 supply parameter meaning. It does a decent job for branch, explaining the document-belongs-to-branch requirement and the inactive-branch exception. However, max_depth (default 12) is never mentioned, leaving one of the two parameters with no semantic explanation anywhere.

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: read the current component object tree (读取当前组件对象树). It adds scope that distinguishes it from document-level siblings by framing the output as the object tree used to get stable IDs or paths. It stops short of naming a concrete sibling as the alternative.

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

Usage Guidelines4/5

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

It gives a clear precondition for use: call this before making modifications in order to obtain stable object IDs or paths. It also states the condition attached to the optional branch argument. There are no explicit exclusions or named alternative tools, so it stays below a 5.

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