Skip to main content
Glama

search_files

Find files by pattern with built-in content previews, respecting .gitignore and filtering by size or date, to explore unfamiliar codebases or analyze build infrastructure without separate read calls.

Instructions

USE INSTEAD OF GLOB/FIND. Find files by pattern with built-in previews - eliminates follow-up read calls.

Respects .gitignore, skips binary files, filters by size/date, handles symlinks safely. Perfect for exploring unfamiliar codebases or analyzing build infrastructure.

Set detail_level="full" to get content previews without separate read calls.

Examples: ".yml" in .github/workflows/, "**/Jenkinsfile", "*.config.js"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasoningYesExplain why you are using this tool - helps track search patterns and improve results
patternYesFile name or glob pattern to match, e.g. "*.ts", "test_*", "src/**/*.config.js"
pathNoDirectory to search in. Defaults to current working directory
include_hiddenNoInclude hidden files and directories (dotfiles). Default: true
ignore_gitignoreNoRespect .gitignore rules and skip ignored files. Default: true
excludeNoAdditional patterns to exclude, e.g. ["node_modules", "dist", "*.log"]
detail_levelNoHow much info to return: "minimal" (paths only), "standard" (+ size/date), "full" (+ content preview)standard
modified_withinNoOnly find files modified within this time, e.g. "24h", "7d", "30m"
min_sizeNoOnly find files larger than this size, e.g. "1MB", "500KB", "1GB"
Behavior4/5

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

No annotations provided, but the description details behavioral traits: respects .gitignore, skips binary files, filters by size/date, handles symlinks safely, and notes that detail_level='full' provides content previews without extra calls.

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 two paragraphs plus examples, front-loaded with key purpose and usage advice. It is fairly concise, though minor restructuring could improve scanability.

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?

With 9 parameters and no output schema, the description covers core functionality, behavioral traits, and key parameter hints. It omits return format details, but the mention of previews and examples partially compensates.

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% and already describes each parameter well. The description adds value by explaining the effect of detail_level='full' and providing examples, but does not significantly augment the schema.

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?

The description explicitly states 'Find files by pattern with built-in previews - eliminates follow-up read calls.' and contrasts with 'glob/find', clearly distinguishing the tool's purpose and scope.

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?

The description advises 'USE INSTEAD OF GLOB/FIND' and provides examples, but does not explicitly contrast with sibling tools like fuzzy_find, search_content, or tree, nor specify 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.

Install Server

Other Tools

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/elad12390/file-search-mcp'

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