directory_tree tool returns flat list instead of recursive tree structure with children

[amcharles91]

The directory_tree tool's implementation doesn't match its documented behavior.

Expected behavior (per tool description):

• Returns a recursive tree view of files and directories
• Each directory entry includes a children array containing its nested items
• Provides a hierarchical JSON structure

Actual behavior:

• Returns only immediate children (non-recursive)
• No children property in the output
• Returns a flat array instead of a tree structure

Current output:
[
{"name": "file1.txt", "type": "file"},
{"name": "subdir", "type": "directory"}
]

Expected output:
[
{"name": "file1.txt", "type": "file"},
{
"name": "subdir",
"type": "directory",
"children": [
{"name": "nested.txt", "type": "file"},
{
"name": "deeper",
"type": "directory",
"children": []
}
]
}
]

This breaks compatibility with the original @modelcontextprotocol/server-filesystem that this project claims to reimplement.

[amcharles91]

Additional critical issue: Even if fixed, the recursive implementation would be unusable on large codebases due to token limits. For example, Unreal Engine with 100k+
files would generate 2-3 million tokens, far exceeding Claude's context window.

Recommended fix should include:

1. Fix the recursive tree structure with children property (as originally intended)
2. Add max_depth parameter (default: 3)
3. Add max_files parameter (default: 1000)
4. Add exclude_patterns parameter (e.g., [".git", "node_modules", "target"])
5. Add include_patterns parameter for filtering by file type

This would make the tool both correct AND practical for real-world use. Without these limits, it's a "token bomb" on any substantial codebase.

[hashemix]

Main issue is fixed in PR #26 and will be included in the next release very soon.
I also added a new optional max_depth parameter to the tool so, depth of directory traversal could be limited.

Regarding other suggestions, I currently don't plan to add additional parameters like max_files, as they go against the intended purpose of the directory_tree tool. Introducing such limits could result in a partial or incomplete representation of the directory structure, potentially omitting some folders and files.

The purpose of directory_tree is to provide a clear representation of the directory's structure. For more flexible operations like searching files by name or pattern, tools such as search_files are better suited and offer more robust functionality.