Skip to main content
Glama
Sign In
ellmos-clatcher-mcp

ellmos-clatcher-mcp

Official
by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

folder_diff

Compare two directories or take a snapshot to detect new, modified, and deleted files between calls.

Instructions

Compare two directories, or take a snapshot and compare on next call. Shows new, modified, and deleted files.

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": {
      "directory": "<directory>"
    },
    "name": "folder_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYesDirectory to compare/snapshot
compare_toNoSecond directory to compare against. Omit for snapshot mode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description must carry burden. It discloses that it shows new/modified/deleted files and has snapshot mode, but does not explicitly state it is read-only or mention performance implications.

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 concise sentences with no unnecessary words. Front-loaded purpose and key details.

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?

Adequately covers purpose and parameters, but missing return format details (no output schema). Fairly complete for a simple diff tool.

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

Parameters4/5

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

Schema coverage is 100%, and description adds clarification on snapshot mode (omit compare_to). Provides context beyond schema, though somewhat redundant.

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?

Description clearly states the tool compares directories with two modes (direct comparison and snapshot), and lists what it shows (new, modified, deleted files). Differentiates from sibling tools like archive or batch_rename.

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?

Describes two usage modes: provide two directories for comparison or omit compare_to for snapshot. Implicitly guides when to use each mode, but lacks explicit alternatives or when-not-to-use.

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