Skip to main content
Glama
MausRundung

Project Explorer MCP Server

by MausRundung

search_files

Search files using pattern matching with regex, file type, size, date filters, and exclude comments or string literals for cleaner code results.

Instructions

Advanced file and code search tool with comprehensive filtering and matching capabilities. Searches for patterns in files within allowed directories with support for regex patterns, file type filtering, size constraints, date filtering, and content preprocessing. When called without arguments, searches for common patterns in the current directory. Supports excluding comments and string literals for cleaner code searches. Results can be formatted as text, JSON, or structured output with configurable sorting and grouping options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternNoSearch pattern - can be literal text or regex depending on regexMode. Defaults to searching for common file types if not specified.*
searchPathNoDirectory path to search in. Must be within allowed directories. Defaults to first allowed directory if not specified
extensionsNoArray of file extensions to include (e.g., ['.js', '.ts', '.py']). Include the dot prefix
excludeExtensionsNoArray of file extensions to exclude
excludePatternsNoArray of filename patterns to exclude (supports simple wildcards)
regexModeNoWhether to treat pattern as a regular expression
caseSensitiveNoWhether search should be case sensitive
wordBoundaryNoWhether to match whole words only
multilineNoWhether to enable multiline regex matching
maxDepthNoMaximum directory recursion depth. Unlimited if not specified
followSymlinksNoWhether to follow symbolic links
includeBinaryNoWhether to search in binary files
minSizeNoMinimum file size in bytes
maxSizeNoMaximum file size in bytes
modifiedAfterNoOnly include files modified after this date (ISO 8601 format)
modifiedBeforeNoOnly include files modified before this date (ISO 8601 format)
snippetLengthNoLength of text snippet around matches
maxResultsNoMaximum number of match results to return
sortByNoHow to sort the resultsrelevance
groupByFileNoWhether to group results by file
excludeCommentsNoWhether to exclude comments from search (language-aware)
excludeStringsNoWhether to exclude string literals from search
outputFormatNoOutput format for resultstext
Behavior4/5

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

With no annotations, the description carries full behavioral burden. It discloses many behavioral traits: regex mode, file/case filtering, exclusion of comments/strings, output formats, and grouping. It could mention performance limitations, but overall provides substantial transparency.

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?

The description is concise (4 sentences) and well-structured, front-loading the primary purpose. Each sentence adds new information: capabilities, default behavior, comment exclusion, and output options, with no unnecessary words.

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?

Given the complexity (23 parameters) and absence of output schema, the description covers a wide range of features and default behavior. It could be more complete by describing the output structure, but it is fairly thorough for a search tool.

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 baseline is 3. The description summarizes the tool's purpose but does not add significant per-parameter detail beyond the existing schema descriptions. It serves as a high-level overview rather than enhancing parameter understanding.

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 clearly identifies the tool as an advanced file and code search tool, specifying its capabilities (regex, filtering, etc.) and default behavior. It distinguishes itself from sibling tools which are unrelated (e.g., delete_file, rename_file), leaving no ambiguity about its purpose.

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 provides clear context for when to use the tool (for file/code search) and mentions default behavior when called without arguments. However, it does not explicitly exclude usage for other tasks or compare with alternatives, though siblings are distinct enough to avoid confusion.

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/MausRundung/mcp-explorer'

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