Skip to main content
Glama
arjshiv

Local Utilities MCP Server

by arjshiv

list_directory

List files and subdirectories in a specified local directory path to view contents and navigate the file system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDirectory path to list

Implementation Reference

  • The asynchronous handler function for the 'list_directory' tool. It extracts the directory path from input parameters, invokes the listDirectory helper, formats the results as JSON, and returns them as text content via the MCP protocol.
    async (params) => {
      // Let SDK handle errors like directory not found
      const dirPath = params.path;
      const contents = await listDirectory(dirPath);
        
      return {
        content: [{
          type: "text",
          text: JSON.stringify({ 
            path: dirPath,
            contents 
          }, null, 2)
        }]
      };
    }
  • The Zod input schema defining the 'path' parameter as a required string for the list_directory tool.
    { path: z.string().describe("Directory path to list") },
  • The registration function that adds the 'list_directory' tool to the McpServer instance, specifying the tool name, input schema, and handler function.
    export function registerDirectoryTool(server: McpServer): void {
      server.tool(
        "list_directory",
        { path: z.string().describe("Directory path to list") },
        async (params) => {
          // Let SDK handle errors like directory not found
          const dirPath = params.path;
          const contents = await listDirectory(dirPath);
            
          return {
            content: [{
              type: "text",
              text: JSON.stringify({ 
                path: dirPath,
                contents 
              }, null, 2)
            }]
          };
        }
      );
    } 
  • Core helper function that asynchronously lists the contents of a directory using Node.js fs.promises, determining entry types (directory, file, other) and file sizes, handling stat errors gracefully.
    export async function listDirectory(dirPath: string): Promise<Array<{ name: string; type: string; size?: number }>> {
      const entries = await fs.promises.readdir(dirPath, { withFileTypes: true });
      
      return Promise.all(entries.map(async (entry) => {
        const entryPath = path.join(dirPath, entry.name);
        
        if (entry.isDirectory()) {
          return { name: entry.name, type: 'directory' };
        } else if (entry.isFile()) {
          try {
            const stats = await fs.promises.stat(entryPath);
            return { 
              name: entry.name, 
              type: 'file',
              size: stats.size
            };
          } catch (statError) {
            // Handle potential stat errors (e.g., broken symlinks)
            console.warn(`Could not stat file ${entryPath}:`, statError);
            return { name: entry.name, type: 'file', size: undefined }; // Indicate file, but size unknown
          }
        } else {
          return { name: entry.name, type: 'other' };
        }
      }));
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/arjshiv/localutils-mcp-server'

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