Skip to main content
Glama

List Directory

list_directory
Read-onlyIdempotent

Lists directory contents with entry type and size information, helping you inspect a path before reading, editing, or validating files.

Instructions

List the entries of a directory with type and size information.

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
pathYesDirectory path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that results include type and size, which is genuinely useful because no output schema exists, but it says nothing about ordering, hidden entries, recursion depth, or failure behavior on a missing/inaccessible path.

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

Conciseness4/5

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

One front-loaded sentence with no filler or redundant restatement of the title. It is efficient, though its brevity leaves room for one short clause on scope without becoming bloated.

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

Completeness3/5

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

This is a low-complexity, single-parameter read tool with rich annotations, so the bar is modest and the description plus annotations cover the essentials. It still leaves the agent guessing about result scope (hidden files, subdirectories) and error conditions, which matters since there is no output schema to fall back on.

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?

There is a single parameter with 100% schema description coverage ("Directory path"), so the schema already carries the semantics. The description adds no clarification about whether relative or absolute paths are accepted, whether trailing separators matter, or whether the path is expanded — baseline 3 applies.

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 specific verb and resource ("List the entries of a directory") and even names the payload (type and size information), so an agent knows exactly what the call produces. It does not differentiate itself from adjacent file-system siblings such as get_file_info or list_tables, but the resource noun is unambiguous on its own.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this when it needs directory contents. There is no statement about when to prefer this over get_file_info or a deeper listing tool, and no mention of preconditions such as whether the path must exist or be readable.

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