Skip to main content
Glama
kucherenko

jscpd

Official
by kucherenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Re-scan the project

check_current_directory
Read-onlyIdempotent

Re-scan the server's configured paths to refresh the clone list and counts, ensuring subsequent duplication queries reflect the current file content.

Instructions

Re-scan the paths the server was started with and return the fresh clone list and counts. Use it after creating, editing or deleting files, so that check_duplication, get_file_clones and get_statistics answer from current content. Returns {files, clones, returned, duplications[]} with the same duplication shape as get_file_clones, biggest first. Reads the filesystem only; it never writes. The scan is synchronous and can take a few seconds on large projects; results replace the previous scan entirely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of clones to include in the response. 'clones' always carries the untruncated total, so a small limit still tells you how much was found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv5.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / default
      Added value: +100
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of clones to include in the response (default 100); 'clones' always carries the untruncated total"New value: +"Maximum number of clones to include in the response. 'clones' always carries the untruncated total, so a small limit still tells you how much was found."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint. The description adds valuable context beyond those: it is synchronous, can take seconds on large projects, reads the filesystem only (reinforcing but not contradicting annotations), and replaces the previous scan entirely. This extra performance and state-replacement info is useful and not redundant.

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?

Four sentences with zero fluff. The primary purpose and usage trigger are front-loaded, followed by output shape, side effects, and performance notes. Every sentence earns its place.

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

Completeness5/5

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

For a tool with one optional parameter and no output schema, the description fully compensates: it specifies the return shape (files, clones, returned, duplications[]), notes the duplication shape matches get_file_clones, and covers time/state behavior. Nothing an agent needs to call it correctly is missing.

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 for the single parameter 'limit' is 100%, with a clear description already explaining its purpose and the untruncated 'clones' field. The description adds no new parameter-specific semantics beyond what the schema provides, so baseline 3 applies.

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 ('Re-scan the paths') and resource ('clone list and counts'), and explicitly ties it to refreshing content for sibling tools (check_duplication, get_file_clones, get_statistics). The purpose is unambiguous and distinct from its siblings.

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

Usage Guidelines5/5

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

Explicitly says 'Use it after creating, editing or deleting files' and explains why (so the other tools answer from current content). This clearly conditions the tool's usage on a specific scenario and establishes its role as a prerequisite, leaving no ambiguity about when to invoke it.

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