Skip to main content
Glama
sergey-fintech

File Finder MCP Server

search_files

Search for files by name fragment to locate specific documents or data in your system.

Instructions

Search for files containing a specified fragment in their names

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fragmentYesText fragment to search for in file names

Implementation Reference

  • Core implementation of the search_files tool logic in the FileFinder class, which recursively walks the directory to find files matching the fragment.
    class FileFinder {
      searchFiles(fragment: string): FileInfo[] {
        const results: FileInfo[] = [];
        this.walkDir('.', fragment, results);
        return results;
      }
    
      private walkDir(dir: string, fragment: string, results: FileInfo[]): void {
        const files = fs.readdirSync(dir, { withFileTypes: true });
        
        for (const file of files) {
          const fullPath = path.join(dir, file.name);
          
          if (file.isDirectory()) {
            this.walkDir(fullPath, fragment, results);
          } else if (file.name.includes(fragment)) {
            const stats = fs.statSync(fullPath);
            results.push({
              name: file.name,
              path: path.resolve(fullPath),
              size: stats.size,
              created: stats.birthtime.toLocaleString()
            });
          }
        }
      }
    }
  • Input schema definition for the search_files tool.
    inputSchema: {
      type: 'object',
      properties: {
        fragment: {
          type: 'string',
          description: 'Text fragment to search for in file names',
        },
      },
      required: ['fragment'],
    },
  • src/index.ts:78-95 (registration)
    Registration of the search_files tool in the ListToolsRequestSchema handler.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'search_files',
          description: 'Search for files containing a specified fragment in their names',
          inputSchema: {
            type: 'object',
            properties: {
              fragment: {
                type: 'string',
                description: 'Text fragment to search for in file names',
              },
            },
            required: ['fragment'],
          },
        },
      ],
    }));
  • MCP CallToolRequestSchema handler that handles calls to search_files, validates parameters, executes the search, and returns results or errors.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      if (request.params.name !== 'search_files') {
        throw new McpError(
          ErrorCode.MethodNotFound,
          `Unknown tool: ${request.params.name}`
        );
      }
    
      const args = request.params.arguments as { fragment: string };
      
      if (!args.fragment) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Missing required parameter: fragment'
        );
      }
    
      try {
        const results = this.fileFinder.searchFiles(args.fragment);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(results, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error('Error searching files:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error searching files: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'search' implies a read-only operation, the description doesn't mention permissions, rate limits, result format, pagination, or error conditions. It lacks essential behavioral context for a search tool.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded with the core purpose.

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?

For a search tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the search returns, how results are formatted, whether there are limitations on search scope, or other behavioral aspects needed for effective use.

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 description coverage is 100%, so the schema already documents the single parameter. The description adds no additional parameter semantics beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting.

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's purpose with a specific verb ('search') and resource ('files'), and specifies the search scope ('containing a specified fragment in their names'). However, there are no sibling tools mentioned, so differentiation from alternatives cannot be assessed.

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, prerequisites, or limitations. It simply states what the tool does without contextual usage information.

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/sergey-fintech/MCP'

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