File Finder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_filesC | Search for files containing a specified fragment in their names |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined, eliminating any ambiguity in tool selection.
The single tool follows a clear verb_noun pattern (search_files), and with no other tools to compare against, consistency is inherently perfect. There are no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'File Finder MCP Server', which suggests a broader scope like file searching, filtering, or management. This minimal set feels thin and underdeveloped for the implied domain.
The tool surface is severely incomplete for a file finder domain. It only supports searching by name fragments, lacking essential operations like filtering by type, size, date, content search, or listing files in directories, which are obvious gaps for the stated purpose.