Skip to main content
Glama
modelcontextprotocol

Filesystem MCP Server

Official

List Directory

list_directory
Read-only

List files and directories in a specified path with clear [FILE] and [DIR] labels to understand directory structure and locate content.

Instructions

Get a detailed listing of all files and directories in a specified path. Results clearly distinguish between files and directories with [FILE] and [DIR] prefixes. This tool is essential for understanding directory structure and finding specific files within a directory. Only works within allowed directories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • The handler function that validates the path, reads directory entries using fs.readdir, formats them with [DIR]/[FILE] prefixes, and returns the formatted list.
    async (args: z.infer<typeof ListDirectoryArgsSchema>) => {
      const validPath = await validatePath(args.path);
      const entries = await fs.readdir(validPath, { withFileTypes: true });
      const formatted = entries
        .map((entry) => `${entry.isDirectory() ? "[DIR]" : "[FILE]"} ${entry.name}`)
        .join("\n");
      return {
        content: [{ type: "text" as const, text: formatted }],
        structuredContent: { content: formatted }
      };
    }
  • Tool registration using server.registerTool, specifying the name 'list_directory', title, description, input/output schemas, annotations, and the handler function.
    server.registerTool(
      "list_directory",
      {
        title: "List Directory",
        description:
          "Get a detailed listing of all files and directories in a specified path. " +
          "Results clearly distinguish between files and directories with [FILE] and [DIR] " +
          "prefixes. This tool is essential for understanding directory structure and " +
          "finding specific files within a directory. Only works within allowed directories.",
        inputSchema: {
          path: z.string()
        },
        outputSchema: { content: z.string() },
        annotations: { readOnlyHint: true }
      },
      async (args: z.infer<typeof ListDirectoryArgsSchema>) => {
        const validPath = await validatePath(args.path);
        const entries = await fs.readdir(validPath, { withFileTypes: true });
        const formatted = entries
          .map((entry) => `${entry.isDirectory() ? "[DIR]" : "[FILE]"} ${entry.name}`)
          .join("\n");
        return {
          content: [{ type: "text" as const, text: formatted }],
          structuredContent: { content: formatted }
        };
      }
    );
  • Zod schema for input arguments of the list_directory tool, defining the required 'path' parameter.
    const ListDirectoryArgsSchema = z.object({
      path: z.string(),
    });
Behavior4/5

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

Annotations provide readOnlyHint=true, indicating it's safe. The description adds valuable behavioral context beyond annotations: it specifies output format details ('Results clearly distinguish between files and directories with [FILE] and [DIR] prefixes') and a constraint ('Only works within allowed directories'), which are not covered by annotations.

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

Conciseness5/5

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

The description is front-loaded with the core purpose, followed by output details and usage context in three efficient sentences. Every sentence adds value without redundancy, making it appropriately sized and well-structured.

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

Completeness5/5

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

Given the tool's low complexity (1 parameter, read-only), annotations covering safety, and the presence of an output schema (which handles return values), the description is complete enough. It covers purpose, output format, usage context, and constraints adequately for the agent's needs.

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

Parameters3/5

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

Schema description coverage is 0%, so the schema provides no parameter details. The description mentions 'specified path' but does not elaborate on path format, allowed values, or examples. It adds minimal meaning beyond the bare schema, resulting in a baseline score.

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 the specific action ('Get a detailed listing') and resource ('files and directories in a specified path'), and distinguishes from siblings by specifying it provides a detailed listing with prefixes, unlike directory_tree (which likely shows hierarchy) or list_directory_with_sizes (which includes size information).

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

Usage Guidelines4/5

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

It provides clear context for when to use ('essential for understanding directory structure and finding specific files within a directory') and mentions a constraint ('Only works within allowed directories'), but does not explicitly name alternatives like list_directory_with_sizes or directory_tree for different needs.

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/modelcontextprotocol/filesystem'

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