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

fgui-agent-bridge

by Wilson520403
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

fgui_find_duplicate

Finds and groups duplicate files by MD5 to clean up repeated imported images, fonts, sounds, and component XML, with each group reporting size, item count, and reclaimable bytes.

Instructions

找出文件内容完全相同的资源，按 MD5 分组（只读，0.8.19+）。

适合清理重复导入的图片、字体和音效；组件 XML 也参与比较。每组返回文件大小、 条目和可回收字节数，按浪费体积从大到小排序。同名不同内容不算重复。

packages / types / include_branches 同 fgui_find_unused；max_groups 和 max_items_per_group 分别限制组数与组内明细条数，计数字段不受截断影响。

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

Input Schema

NameRequiredDescriptionDefault
typesNo
packagesNo
max_groupsNo
include_branchesNo
max_items_per_groupNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.25

TDQS

A4.1/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 declares the operation read-only (只读), gates it to version 0.8.19+, states results are sorted by wasted bytes descending, and clarifies that count fields are not affected by truncation. It does not say whether flagged duplicates are safe to delete automatically or what happens to references.

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 core definition and scope, then use case, then behaviour, then parameters. Every sentence adds information; only the cross-reference to fgui_find_unused leaves work undone rather than being wasteful.

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 analysis tool with an output schema, the description covers what is compared, how groups are ordered, truncation semantics, and version gating. The remaining gap is the meaning of three filter parameters and the safety of acting on results.

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 for 5 parameters. It explains max_groups and max_items_per_group well (group count vs. per-group detail, counts unaffected by truncation) but defers packages/types/include_branches entirely to fgui_find_unused, forcing the agent to consult another definition to resolve three parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: find resources with byte-identical content, grouped by MD5. The line '同名不同内容不算重复' (same name, different content is not a duplicate) explicitly separates it from fgui_duplicate_package_item and other duplicate-named siblings, so an agent can choose correctly without opening schemas.

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?

Gives a concrete use case (cleaning up re-imported images, fonts, sounds) and notes that component XML is also compared. It points to fgui_find_unused as the reference for shared parameters but never states when NOT to use this tool or what to do before deleting results.

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