Skip to main content
Glama
Sign In
fast-filesystem-mcp

fast-filesystem-mcp

by efforthye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fast_find_large_files

Scan a directory to find files exceeding a specified size, such as 100MB. Return a configurable number of results to identify storage-intensive files quickly.

Instructions

Finds large 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": {
      "path": "<path>"
    },
    "name": "fast_find_large_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDirectory to search in
min_sizeNoMinimum size (e.g., 100MB, 1GB)100MB
max_resultsNoMaximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • changedInput schema / properties / max_results / description
      Previous value: -"최대 결과 수"New value: +"Maximum number of results"
    • changedInput schema / properties / min_size / description
      Previous value: -"최소 크기 (예: 100MB, 1GB)"New value: +"Minimum size (e.g., 100MB, 1GB)"
    • changedInput schema / properties / path / description
      Previous value: -"검색할 디렉토리"New value: +"Directory to search in"
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states 'Finds large files' without explaining crucial behavior such as recursion behavior, permission handling, or performance implications. This is insufficient for an agent to understand side effects or prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is too brief for the tool's complexity. While conciseness is valued, this sentence lacks essential details and does not earn its place as it is merely a restatement of the tool name without adding context.

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?

Given the presence of three parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain the return format, how min_size is interpreted, or any limitations, leaving significant gaps for an agent to use the tool correctly.

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?

The input schema provides full documentation for all three parameters (path, min_size, max_results) with descriptions. The tool description adds no extra meaning beyond what the schema already provides. As schema coverage is 100%, the baseline is 3.

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 'Finds large files' clearly states a specific verb and resource (finding files by size). It is concise but lacks explicit differentiation from sibling tools like fast_search_files, which may also find files based on other criteria. However, the purpose is still clear enough.

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?

No guidance is provided on when to use this tool versus alternatives such as fast_search_files or fast_list_directory. The description does not mention any exclusions or prerequisites, leaving the agent without context on appropriate usage scenarios.

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