Skip to main content
Glama
ai-yliu

Filesystem MCP Server

by ai-yliu

list_allowed_directories

Lists directories accessible to the Filesystem MCP Server for file operations. Use this tool to identify available paths for reading, writing, or managing files.

Instructions

List all directories the server is allowed to access

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'list_allowed_directories' tool. Returns a JSON-formatted list of the resolved allowed directories as text content.
    case 'list_allowed_directories': {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(resolvedAllowedDirectories, null, 2),
          },
        ],
      };
    }
  • src/index.ts:222-230 (registration)
    Tool registration in the ListTools response, defining the name, description, and empty input schema for 'list_allowed_directories'.
    {
      name: 'list_allowed_directories',
      description: 'List all directories the server is allowed to access',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Definition of resolvedAllowedDirectories, which is used by the tool handler to list the allowed access directories.
    const resolvedAllowedDirectories = allowedDirectories.map(dir => path.resolve(dir));
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. It states the tool lists directories, implying a read-only operation, but doesn't specify whether this requires authentication, what the output format is (e.g., list of paths, JSON structure), or if there are rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, clear sentence that directly states the tool's purpose without any fluff or redundancy. It's front-loaded and efficiently communicates the essential information, making it highly concise and well-structured.

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?

Given the tool has 0 parameters, no annotations, and no output schema, the description is minimally adequate by stating what the tool does. However, it lacks details on behavioral aspects like output format or usage context, which are important for an agent to invoke it correctly. It meets the basic requirement but leaves gaps in completeness.

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, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly avoids mentioning any. A baseline of 4 is appropriate as it doesn't mislead or omit necessary parameter information.

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 clearly states the action ('List') and the resource ('all directories the server is allowed to access'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_directory' or 'search_files', which might also list directories but with different scopes or filters, preventing a perfect score.

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 such as 'list_directory' (which might list contents of a specific directory) or 'search_files' (which might filter results). There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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/ai-yliu/filesystem-mcp-server'

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