Skip to main content
Glama

fast_list_allowed_directories

Lists directories accessible for file operations in the filesystem MCP server, enabling users to identify available paths for reading or writing files.

Instructions

Lists the allowed directories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'fast_list_allowed_directories' tool. It returns the list of allowed directories, exclude patterns, and server configuration limits.
    async function handleListAllowedDirectories() {
      return {
        allowed_directories: DEFAULT_ALLOWED_DIRECTORIES,
        current_working_directory: process.cwd(),
        exclude_patterns: DEFAULT_EXCLUDE_PATTERNS,
        claude_limits: {
          max_response_size_mb: CLAUDE_MAX_RESPONSE_SIZE / (1024**2),
          max_chunk_size_mb: CLAUDE_MAX_CHUNK_SIZE / (1024**2),
          max_lines_per_read: CLAUDE_MAX_LINES,
          max_dir_items: CLAUDE_MAX_DIR_ITEMS
        },
        server_info: {
          name: 'fast-filesystem',
          version: '2.1.0',
          total_tools: MCP_TOOLS.length,
          timestamp: new Date().toISOString()
        }
      };
    }
  • api/server.ts:320-322 (registration)
    The switch case in the tools/call handler that dispatches to the tool's handler function.
    case 'fast_list_allowed_directories':
      result = await handleListAllowedDirectories();
      break;
  • api/server.ts:99-106 (registration)
    Registration of the tool in the MCP_TOOLS array, including name, description, and empty input schema (no parameters required).
      name: 'fast_list_allowed_directories',
      description: '허용된 디렉토리 목록을 조회합니다',
      inputSchema: { 
        type: 'object', 
        properties: {}, 
        required: [] 
      }
    },
  • The input schema for the tool, which is an empty object since no parameters are required.
      type: 'object', 
      properties: {}, 
      required: [] 
    }
  • Helper constant defining the default allowed directories, which is returned by the handler.
    const DEFAULT_ALLOWED_DIRECTORIES = [
      process.env.HOME || '/home',
      '/tmp',
      '/Users', 
      '/home'
    ];
  • Helper constant defining default exclude patterns for paths, returned by the handler.
    const DEFAULT_EXCLUDE_PATTERNS = [
      '.venv', 'venv', 'node_modules', '.git', '.svn', '.hg',
      '__pycache__', '.pytest_cache', '.mypy_cache', '.coverage',
      'dist', 'build', 'target', 'bin', 'obj', '.vs', '.vscode',
      '*.pyc', '*.pyo', '*.pyd', '.DS_Store', 'Thumbs.db'
    ];
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Lists' suggests a read-only operation, but the description doesn't clarify what 'allowed directories' means in practice - whether this refers to user permissions, system restrictions, or some other access control mechanism. It doesn't mention pagination, rate limits, authentication requirements, or what format the results will be in. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 maximally concise - a single sentence with no wasted words. It's front-loaded with the core functionality. Every word earns its place, making it easy for an AI agent to parse quickly. This is an excellent example of efficient communication.

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, no output schema, and the description's minimal content, this is incomplete for effective tool selection. While the tool has no parameters (simplifying one aspect), the description doesn't explain what 'allowed directories' means, how results are structured, or when this tool should be chosen over similar directory listing tools. For a tool in a server with many file/directory operations, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. This meets the baseline expectation for a parameterless tool, though it doesn't add any additional context about why no parameters are needed.

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

Purpose3/5

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

The description 'Lists the allowed directories' clearly states the action (lists) and resource (allowed directories), which is adequate for understanding the basic function. However, it doesn't distinguish this tool from sibling tools like 'fast_list_directory' or 'fast_get_directory_tree' - it's unclear what makes 'allowed directories' different from regular directory listings. The purpose is clear but lacks sibling differentiation.

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. With multiple directory-related tools in the sibling list (fast_list_directory, fast_get_directory_tree, fast_get_disk_usage), there's no indication of when 'allowed directories' is the appropriate choice versus general directory listing tools. No context about prerequisites, permissions, or typical use cases is provided.

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

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