Skip to main content
Glama

find_duplicates

Read-only

Identifies identical files in a folder and groups them by reclaimable space without deleting anything. Review duplicate groups before manual cleanup.

Instructions

Find identical files in a folder, grouped by reclaimable space. Deletes nothing.

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
min_sizeNo
extensionsNo
max_groupsNo
include_vendorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this is a safe read, and 'Deletes nothing' largely restates that. The description does add one real behavioral fact — results are grouped by reclaimable space — but says nothing about how 'identical' is determined (content hash vs name/size), whether subfolders or symlinks are traversed, or how the scan scales, which matters for a filesystem walk.

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 wasted words, and the scoping statement leads. It is efficient, though the brevity is achieved partly by dropping the filter and behavior detail that the zero-coverage schema needed.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a filesystem-scanning tool with five parameters, no documented schema fields, and no output schema, the definition is too thin: an agent cannot tell what min_size, extensions, max_groups, or include_vendor do, nor what the grouping structure will look like. Only the core purpose and the no-deletion guarantee are covered.

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?

Schema description coverage is 0% across five parameters, so the description carries the full burden and does not meet it. The four optional filters (min_size, extensions, max_groups, include_vendor) are never mentioned, leaving an agent to guess from bare parameter names; only 'path' is implicitly covered by 'in a folder'.

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 gives a specific verb and resource ('Find identical files in a folder') plus an output-shaping detail ('grouped by reclaimable space'), so an agent knows exactly what the tool returns at a glance. It stops short of differentiating from any near-neighbor such as image_compare or diff, but the purpose itself is unambiguous.

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?

'Deletes nothing' signals a safe pre-cleanup inspection use case, which implicitly tells an agent this is a discovery step rather than a dedupe action. However there is no explicit when-to-use/when-not guidance, no mention of a follow-up tool for actually removing duplicates, and no stated prerequisites beyond a path.

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