FileScopeMCP
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 |
|---|---|
| list_saved_treesB | List all saved file trees |
| delete_file_treeC | Delete a file tree configuration |
| create_file_treeC | Create or load a file tree configuration |
| select_file_treeC | Select an existing file tree to work with |
| list_filesB | List all files in the project with their importance rankings |
| get_file_importanceC | Get the importance ranking of a specific file |
| find_important_filesC | Find the most important files in the project |
| get_file_summaryC | Get the summary of a specific file |
| set_file_summaryC | Set the summary of a specific file |
| read_file_contentC | Read the content of a specific file |
| set_file_importanceC | Manually set the importance ranking of a specific file |
| recalculate_importanceB | Recalculate importance values for all files based on dependencies |
| debug_list_all_filesB | List all file paths in the current file tree |
| generate_diagramC | Generate a Mermaid diagram for the current file tree |
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 14 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools like 'create_file_tree', 'delete_file_tree', and 'select_file_tree' handle tree management, while 'read_file_content', 'get_file_summary', and 'set_file_summary' focus on file content operations. The separation between listing functions ('debug_list_all_files', 'list_files', 'list_saved_trees') and importance calculations ('get_file_importance', 'set_file_importance', 'recalculate_importance') is well-defined, preventing misselection.
All tool names follow a consistent verb_noun pattern with snake_case throughout. Verbs like 'create', 'delete', 'list', 'get', 'set', 'read', 'find', 'generate', 'select', and 'recalculate' are used predictably with corresponding nouns. There are no deviations in naming conventions, making the tool set highly readable and predictable.
With 14 tools, the count is well-scoped for managing file trees and analyzing file importance in a project. Each tool earns its place by covering distinct aspects such as tree configuration, file listing, content access, importance ranking, and diagram generation. This number is neither too sparse nor overwhelming, fitting the server's purpose effectively.
The tool surface provides complete CRUD/lifecycle coverage for file tree management and file analysis. It includes creation, selection, listing, and deletion of trees, along with operations for reading, summarizing, and setting importance for files. Tools like 'recalculate_importance' and 'generate_diagram' add advanced functionality, leaving no obvious gaps that would cause agent failures in this domain.