deep-directory-tree-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_deep_directory_treeC | Get deep directory 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 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly distinct by default.
A single tool inherently follows a consistent naming pattern, as there are no other tools to compare against. The name 'get_deep_directory_tree' uses a clear verb_noun structure.
One tool is too few for a server named 'deep-directory-tree-mcp', which suggests a scope that might include operations like listing, filtering, or modifying directory trees. A single get operation feels thin and incomplete for this domain.
The tool surface is severely incomplete for a directory tree domain. It only provides a get operation, with obvious gaps such as creating, updating, deleting, or searching directory trees, which are essential for basic CRUD coverage.