Shell MCP

listDir

List directory contents with metadata (type, size, modification date). Non-recursive exploration to verify filesystem structure.

Instructions

List the contents of a directory with metadata for each entry. Returns a formatted table with columns: Type (d=directory, l=symlink, -=file), Size (bytes), Modified (ISO datetime), and Name. Use this to explore the filesystem, discover files, or verify directory structure. Does not recurse into subdirectories — call again on child directories for deeper exploration. Paths targeting sensitive system directories (e.g. /proc/, /sys/, /dev/) are blocked.

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": "listDir"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute or relative path to the directory to list. Relative paths are resolved from the server's working directory. Must not be empty or contain null bytes. Examples: `.`, `/home/user/projects`, `./src`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4May 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, description carries full burden. It discloses non-recursion, blocked sensitive system paths, and output format (formatted table with columns). No contradiction with annotations (none present). Missing discussion of error behavior or performance, but adequate for a list tool.

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?

Four sentences with clear front-loading: purpose + output, usage, recursion guidance, security. No redundant information. Each sentence serves a distinct purpose.

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

Completeness4/5

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

Given no annotations or output schema, the description covers essential aspects: what it does, how to use path, what it returns, limitations (non-recursion, blocked paths). Minor omission: doesn't specify behavior for invalid paths, but overall complete.

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 coverage is 100%, so baseline is 3. The description reinforces path usage (absolute/relative, empty/null byte restrictions) but does not add new semantics beyond the schema explanation. The examples in schema are sufficient.

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?

Clearly states 'List the contents of a directory with metadata for each entry', specifying verb and resource. The columns (Type, Size, Modified, Name) make the output explicit. Distinguishes from sibling tools like readFile and exec by focusing on directory listing.

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?

Describes when to use: 'explore the filesystem, discover files, or verify directory structure'. Explicitly warns that it does not recurse and instructs to call again on child directories. No missing exclusions or comparisons to siblings, but context is clear.

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

Deploy Server