Skip to main content
Glama

find_duplicates

Read-only

Scans a folder path to group identical files, marks the first in each group as the original to keep, and surfaces duplicates for cleanup.

Instructions

Groups of identical files. The first in each group is the original and is kept.

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": {
      "path": "<path>"
    },
    "name": "find_duplicates"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
groupsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • removedOutput schema / $defs / FileInfo / properties / path / format
      Removed value: -"path"
  2. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add one genuinely useful behavioral fact beyond them: the first file in each group is designated the original and is kept, which signals which files are candidates for removal. It still omits recursion depth, tie-breaking rules, and whether hidden/system files are considered.

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?

Two short sentences with no filler, and the grouping concept is stated first with the keep-original rule second. It is terse but not padded; the brevity works against it only in coverage, not in structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 original-is-kept rule covers the most consequential semantic. However, a 1-parameter tool with no documented parameter, no scope statement, and no stated relationship to plan_tidy/apply_plan remains incomplete for the workflow it belongs to.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter 'path' has 0% schema description coverage and the description never mentions it, so nothing indicates whether it is a file, a directory root, and whether traversal is recursive. With one undocumented parameter the description was the only place to compensate and it does not.

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

Purpose3/5

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

The description conveys the concept (grouping identical files) but is a noun phrase without a verb articulating the operation or its scope — 'path' is a required argument yet the description never says the groups are produced for files under that path. It does not differentiate from sibling scan_folder, which an agent could plausibly pick instead when looking for file analysis.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the sibling workflow (plan_tidy/apply_plan/undo) that this tool presumably feeds. The agent is left to infer that this is a read-only analysis step preceding a tidy plan.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.