Skip to main content
Glama
talentedmrweb

Local Dev Bridge MCP

list_directory

Browse files and directories in a specified path to view local project contents for development tasks.

Instructions

List files and directories in a given path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to directory (relative to projects directory or absolute)

Implementation Reference

  • The handler function that implements the list_directory tool logic: resolves path, reads directory entries, formats with icons, and returns formatted text content.
    async listDirectory(dirPath) {
      const resolvedPath = this.resolvePath(dirPath);
      const entries = await fs.readdir(resolvedPath, { withFileTypes: true });
      
      const items = entries.map((entry) => {
        const icon = entry.isDirectory() ? '📁' : '📄';
        return `${icon} ${entry.name}`;
      });
      
      return {
        content: [
          {
            type: 'text',
            text: `Contents of ${resolvedPath}:\n\n${items.join('\n')}`,
          },
        ],
      };
    }
  • Input schema for the list_directory tool defining the 'path' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        path: {
          type: 'string',
          description: 'Path to directory (relative to projects directory or absolute)',
        },
      },
      required: ['path'],
    },
  • index.js:101-114 (registration)
    Registration of the list_directory tool metadata (name, description, schema) in the ListToolsRequestSchema response.
    {
      name: 'list_directory',
      description: 'List files and directories in a given path',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path to directory (relative to projects directory or absolute)',
          },
        },
        required: ['path'],
      },
    },
  • index.js:172-173 (registration)
    Dispatch/registration of the list_directory handler in the CallToolRequestSchema switch statement.
    case 'list_directory':
      return await this.listDirectory(args.path);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('List') but lacks details on permissions, error handling, output format, pagination, or whether it's read-only. This is a significant gap for a tool with no structured safety hints.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded and appropriately sized for a simple tool, with zero waste.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like what the output looks like (e.g., list format, error cases), permissions needed, or how it differs from siblings. For a tool with no structured context, more detail is warranted.

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?

The input schema has 100% description coverage, with the 'path' parameter well-documented in the schema itself. The description adds minimal value beyond implying the path is for listing contents, but it doesn't provide additional context like path validation or examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('List') and resource ('files and directories'), and it specifies the scope ('in a given path'). However, it doesn't explicitly distinguish this from sibling tools like 'search_files' or 'read_file', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like browsing directory contents versus searching for specific files, nor does it reference sibling tools such as 'search_files' for filtered queries or 'read_file' for file content access.

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/talentedmrweb/local-dev-bridge-mcp'

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