Skip to main content
Glama
Sign In
Claude File Manager MCP

Claude File Manager MCP

by sadd11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Find files by name

find_files

Locate files by glob pattern or partial name across a directory tree, skipping service folders like node_modules, .git, and .mcp. Use it to find source files, configs, or docs quickly.

Instructions

Finds files by glob (*.js, src/**/*.ts, config*) or a substring in the name. Service folders (node_modules, .git, .mcp) are skipped.

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": {
      "pattern": "<pattern>"
    },
    "name": "find_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoWhere to search (defaults to root).
ignoreNoAdditional names/globs to skip
patternYesGlob (`*.md`, `**/*.js`) or part of the name
max_depthNoMaximum depth
max_resultsNoMaximum number of results
include_dirsNoInclude folders in the results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that node_modules, .git, and .mcp are skipped by default — information found nowhere in the schema — but it omits whether results are sorted, whether hidden files are included, whether paths returned are absolute or relative to `path`, and how invalid globs are handled.

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 sentences, both load-bearing: the first defines the matching semantics, the second discloses the default exclusions. Nothing is padded or repeated.

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?

For a six-parameter, annotation-free tool with no output schema, the definition covers the matching contract and default exclusions but leaves the return shape (path format, ordering) and edge-case behavior unexplained. Adequate to invoke, not complete enough to predict results confidently.

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 100%, so all six parameters already carry descriptions including defaults and min/max bounds. The description's only addition is restating that `pattern` accepts glob or substring, which duplicates the schema text, so the baseline 3 applies.

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?

States a specific verb and resource ("Finds files") and immediately qualifies the two matching modes with concrete examples (`*.js`, `src/**/*.ts`, `config*`, substring). It does not explicitly distinguish itself from name-similar siblings like list_directory or search_content, so it stops short of a 5.

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?

The pattern examples imply the intended usage (name-based lookup), but there is no explicit statement of when to choose this over list_tree/list_directory or search_content for content matching. The agent must infer the routing decision from tool names alone.

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