file_reader_mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesD | – |
| read_fileD | – |
| search_filesD | – |
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 3 tools
Each tool has a clearly distinct purpose: listing files, reading file contents, and searching for files. No overlap or ambiguity.
All tools follow a verb_noun pattern, but read_file uses singular 'file' while list_files and search_files use plural 'files'. This minor inconsistency prevents a perfect score.
Three tools is well-scoped for a file reader server. Each tool serves a core need without redundancy or bloat.
For a read-only file server, the surface covers listing, reading, and searching—all essential operations. No obvious gaps for the stated purpose.