mcp-file-oper
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 |
|---|---|
| view_fileC | View a text file at the specified path |
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 'view_file' has a single, clear purpose that cannot be mistaken for any other functionality within this server.
The single tool name 'view_file' follows a clear verb_noun pattern (view + file). Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'mcp-file-oper', which suggests broader file operations. The scope implied by the name includes actions like create, delete, edit, or list files, but only viewing is provided, making the tool count insufficient for the apparent domain.
The server is severely incomplete for file operations, as it only offers viewing with no ability to create, update, delete, list, or manage files. This creates significant gaps that will cause agent failures when attempting common file-related tasks beyond simple viewing.