Skip to main content
Glama
efforthye
by efforthye

fast_search_files

Search for files in a directory by name or content using regex patterns, with auto-chunking, context lines, and line numbers to find matches quickly.

Instructions

Searches for files (by name/content) - supports auto-chunking, regex, context, and line numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDirectory to search in
patternYesSearch pattern (regex supported)
content_searchNoSearch file content
case_sensitiveNoCase-sensitive search
max_resultsNoMaximum number of results
context_linesNoNumber of context lines around a match
file_patternNoFilename filter pattern (e.g., *.js, *.txt)
include_binaryNoInclude binary files in search
continuation_tokenNoContinuation token from a previous call
auto_chunkNoEnable auto-chunking

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv1.0.0
    • changedInput schema / properties / auto_chunk / description
      Previous value: -"자동 청킹 활성화"New value: +"Enable auto-chunking"
    • changedInput schema / properties / case_sensitive / description
      Previous value: -"대소문자 구분"New value: +"Case-sensitive search"
    • changedInput schema / properties / content_search / description
      Previous value: -"파일 내용 검색"New value: +"Search file content"
    • changedInput schema / properties / context_lines / description
      Previous value: -"매치된 라인 주변 컨텍스트 라인 수"New value: +"Number of context lines around a match"
    • changedInput schema / properties / continuation_token / description
      Previous value: -"이전 호출의 연속 토큰"New value: +"Continuation token from a previous call"
    • changedInput schema / properties / file_pattern / description
      Previous value: -"파일명 필터 패턴 (*.js, *.txt 등)"New value: +"Filename filter pattern (e.g., *.js, *.txt)"
    • changedInput schema / properties / include_binary / description
      Previous value: -"바이너리 파일 포함 여부"New value: +"Include binary files in search"
    • changedInput schema / properties / max_results / description
      Previous value: -"최대 결과 수"New value: +"Maximum number of results"
    • changedInput schema / properties / path / description
      Previous value: -"검색할 디렉토리"New value: +"Directory to search in"
    • changedInput schema / properties / pattern / description
      Previous value: -"검색 패턴 (정규표현식 지원)"New value: +"Search pattern (regex supported)"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It mentions key features (auto-chunking, regex, context, line numbers) but does not disclose read-only behavior, result structure, or potential performance impacts.

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?

The description is a single sentence that packs multiple features, which is concise. However, it could be better organized (e.g., break into two sentences) for readability.

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?

Despite 10 parameters and no output schema, the description does not explain the return format (e.g., file paths, line numbers, content snippets) or how continuation tokens work. Significant gaps remain.

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%, so baseline is 3. The description adds value by summarizing features (auto-chunking, regex, context) that map to parameters, providing thematic context beyond the schema.

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 clearly states the tool searches for files by name or content, and lists supported features. It distinguishes from sibling 'fast_search_code' implicitly, but could more explicitly differentiate.

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?

The description provides no guidance on when to use this tool versus alternatives like 'fast_search_code' or when not to use it. It lacks any usage context.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/efforthye/fast-filesystem-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server