Skip to main content
Glama
efforthye
by efforthye

fast_list_directory

List directory contents with pagination, filtering, sorting, and automatic chunking for large directories. Supports hidden files and continuation tokens for efficient browsing.

Instructions

Lists the contents of a directory (with auto-chunking and pagination support)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDirectory path
pageNoPage number
page_sizeNoNumber of items per page
patternNoFilename filter pattern
show_hiddenNoShow hidden files
sort_byNoSort byname
reverseNoReverse sort order
continuation_tokenNoContinuation token from a previous call
auto_chunkNoEnable auto-chunking

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv1.0.0
    • changedInput schema / properties / auto_chunk / description
      Previous value: -"자동 청킹 활성화"New value: +"Enable auto-chunking"
    • changedInput schema / properties / continuation_token / description
      Previous value: -"이전 호출의 연속 토큰"New value: +"Continuation token from a previous call"
    • changedInput schema / properties / page / description
      Previous value: -"페이지 번호"New value: +"Page number"
    • changedInput schema / properties / page_size / description
      Previous value: -"페이지당 항목 수"New value: +"Number of items per page"
    • changedInput schema / properties / path / description
      Previous value: -"디렉토리 경로"New value: +"Directory path"
    • changedInput schema / properties / pattern / description
      Previous value: -"파일명 필터 패턴"New value: +"Filename filter pattern"
    • changedInput schema / properties / reverse / description
      Previous value: -"역순 정렬"New value: +"Reverse sort order"
    • changedInput schema / properties / show_hidden / description
      Previous value: -"숨김 파일 표시"New value: +"Show hidden files"
    • changedInput schema / properties / sort_by / description
      Previous value: -"정렬 기준"New value: +"Sort by"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description adds auto-chunking and pagination support beyond what annotations (none) provide, but it does not disclose read-only nature, required permissions, or limitations like what happens if the path is invalid.

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?

A single concise sentence that is front-loaded with the core action and key features. No redundant or extraneous information.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description fails to explain the return format, pagination mechanics, or how pattern matching works. It is insufficient for effective agent use.

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?

With 100% schema description coverage, the input schema already explains each parameter. The description adds only a high-level mention of auto-chunking and pagination, which adds minimal value beyond the schema.

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?

The description explicitly states the tool lists directory contents and mentions auto-chunking and pagination, which clearly distinguishes it from sibling tools like 'fast_get_directory_tree'.

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?

No guidance is provided on when to use this tool versus alternatives, such as comparing with 'fast_get_directory_tree' or 'fast_get_file_info'. There are no exclusions or prerequisites mentioned.

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

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/efforthye/fast-filesystem-mcp'

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