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

fgui-agent-bridge

by Wilson520403
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

fgui_create_group

Creates a group from unlocked, ungrouped objects under at least two root components and reports member ownership and order; can save and reload to verify results.

Instructions

将至少两个根组件下未锁定、未分组对象组成组（0.8.24+）。

targets 每项仅含 id/name/path 一个定位键。原生操作把成员移到显示列表末尾。 返回成员归属和前后顺序；不进 Agent 撤销栈。save 保存整个当前文档； external_reload 需 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": {
      "targets": "<targets>"
    },
    "name": "fgui_create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
saveNo
verifyNo
targetsYes
external_reloadNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.25

TDQS

A4.1/5.0
Behavior5/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 so well: it discloses the native side effect (members moved to the end of the display list), that the call does not enter the Agent undo stack, that save writes the entire document, and that external_reload requires save=True plus a close/reopen check. These are exactly the non-obvious mutation behaviors an agent needs.

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 the operation and constraints, then side effects, return info, and save/reload semantics in dense but purposeful sentences. No filler, though the compression makes some clauses (e.g., the targets locator rule) easy to skim past.

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?

A mutation tool with an output schema and no annotations; the description covers side effects, undo behavior, persistence, and reload verification, which is most of what matters. The remaining gap is 'verify' semantics and whether 'name' is required or auto-generated, but the core is complete.

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%, so the description must compensate, and it does for targets (exactly one locator key of id/name/path), save (whole-document save), and external_reload (requires save=True). It leaves 'name' and 'verify' entirely undocumented, leaving two of five parameters unexplained.

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?

Uses a concrete verb and resource ('将…对象组成组') and adds precise preconditions: at least two, unlocked, ungrouped, under root components, version 0.8.24+. The purpose is unmistakable, though it doesn't explicitly contrast with the closest sibling, fgui_set_group_layout.

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?

States clear preconditions for use (minimum two objects, unlocked, ungrouped, root-component scope) which effectively defines when this applies. It stops short of naming alternatives or exclusions such as set_group_layout or duplicate_object, so an agent must infer sibling routing.

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