Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

list-directory

Lists files and subdirectories at a specified path so you can inspect directory contents before reading, editing, or managing local files.

Instructions

List contents of a directory

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "list-directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden, yet it says nothing about recursion, hidden-file handling, ordering, or error behavior for missing paths. Only the fact that it is a listing (implicitly read-only) can be inferred from the name and description.

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

Conciseness3/5

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

One short, front-loaded sentence with no wasted words, but it is terse to the point of under-specification rather than efficiently informative.

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?

There is no output schema, so the description is the only place an agent could learn what a listing returns (names only, metadata, sizes), and it does not say. For a tool whose entire value is its output shape, this is a meaningful gap.

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 single path parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description adds no format, relative-vs-absolute, or root-path detail beyond the schema.

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 states a concrete verb and resource ("List contents of a directory"), which is unambiguous about the operation. It does not differentiate from nearby siblings such as read-file or list-indexes, so an agent gets the purpose but not the boundary.

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?

There is no guidance on when to use this tool versus read-file or search-documents, and no mention of prerequisites or behavior on invalid paths. The only implied usage is the obvious case of enumerating a folder.

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