Skip to main content
Glama
GongRzhe

Terminal Controller for MCP

list_directory

List the files and subdirectories in any directory to inspect its contents.

Instructions

List files and subdirectories in the specified directory

Args:
    path: Directory path to list contents, default is current directory

Returns:
    List of directory contents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo

Implementation Reference

  • The `list_directory` tool handler function, decorated with @mcp.tool(). Lists files and subdirectories in a given path (or current directory), returning a formatted string with 📁 for dirs and 📄 for files, sorted alphabetically.
    @mcp.tool()
    async def list_directory(path: Optional[str] = None) -> str:
        """
        List files and subdirectories in the specified directory
        
        Args:
            path: Directory path to list contents, default is current directory
        
        Returns:
            List of directory contents
        """
        if path is None:
            path = os.getcwd()
        
        try:
            items = os.listdir(path)
            
            dirs = []
            files = []
            
            for item in items:
                full_path = os.path.join(path, item)
                if os.path.isdir(full_path):
                    dirs.append(f"📁 {item}/")
                else:
                    files.append(f"📄 {item}")
            
            # Sort directories and files
            dirs.sort()
            files.sort()
            
            if not dirs and not files:
                return f"Directory '{path}' is empty"
            
            output = f"Contents of directory '{path}':\n\n"
            
            if dirs:
                output += "Directories:\n"
                output += "\n".join(dirs) + "\n\n"
            
            if files:
                output += "Files:\n"
                output += "\n".join(files)
            
            return output
        
        except FileNotFoundError:
            return f"Error: Directory '{path}' does not exist"
        except PermissionError:
            return f"Error: No permission to access directory '{path}'"
        except Exception as e:
            return f"Error listing directory contents: {str(e)}"
  • The registration is via the `@mcp.tool()` decorator on line 201, which registers `list_directory` as an MCP tool on the FastMCP server instance named 'mcp' (initialized on line 11).
    @mcp.tool()
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations present, so description carries full burden. It does not disclose whether listing is recursive, what format the output uses (names only? paths?), or error handling. This is insufficient for a tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus structured Args/Returns. Front-loaded with purpose. Returns is vague but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one param and no output schema, the description covers basic usage. However, it omits details like hidden files, sorting, or error cases, which are relevant for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds meaning: clarifies path is a directory path, default is current directory. This compensates for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists files and subdirectories, which is a specific verb and resource. It distinguishes itself from sibling tools like read_file and write_file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: use to list directory contents. No explicit when-not-to-use or alternatives provided, but the context is straightforward.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GongRzhe/terminal-controller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server