Skip to main content
Glama
modelcontextprotocol

Filesystem MCP Server

Official

List Allowed Directories

list_allowed_directories
Read-only

Discover accessible directories and their subdirectories in the Filesystem MCP Server to verify available paths before file operations.

Instructions

Returns the list of directories that this server is allowed to access. Subdirectories within these allowed directories are also accessible. Use this to understand which directories and their nested paths are available before trying to access files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • The inline async handler function for the 'list_allowed_directories' tool. It formats and returns the list of allowed directories as text content.
    async () => {
      const text = `Allowed directories:\n${allowedDirectories.join('\n')}`;
      return {
        content: [{ type: "text" as const, text }],
        structuredContent: { content: text }
      };
    }
  • Input and output schema definition for the 'list_allowed_directories' tool. No input parameters required, outputs string content.
    {
      title: "List Allowed Directories",
      description:
        "Returns the list of directories that this server is allowed to access. " +
        "Subdirectories within these allowed directories are also accessible. " +
        "Use this to understand which directories and their nested paths are available " +
        "before trying to access files.",
      inputSchema: {},
      outputSchema: { content: z.string() },
      annotations: { readOnlyHint: true }
  • The server.registerTool call that registers the 'list_allowed_directories' tool, including its schema and inline handler implementation.
    server.registerTool(
      "list_allowed_directories",
      {
        title: "List Allowed Directories",
        description:
          "Returns the list of directories that this server is allowed to access. " +
          "Subdirectories within these allowed directories are also accessible. " +
          "Use this to understand which directories and their nested paths are available " +
          "before trying to access files.",
        inputSchema: {},
        outputSchema: { content: z.string() },
        annotations: { readOnlyHint: true }
      },
      async () => {
        const text = `Allowed directories:\n${allowedDirectories.join('\n')}`;
        return {
          content: [{ type: "text" as const, text }],
          structuredContent: { content: text }
        };
      }
    );
Behavior4/5

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

The description adds valuable behavioral context beyond the readOnlyHint annotation. It clarifies that subdirectories within allowed directories are also accessible, which is important operational information not captured in annotations. However, it doesn't mention potential limitations like rate limits or authentication requirements, though the annotation covers the safety aspect adequately.

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 perfectly concise with two well-structured sentences. The first sentence states the core functionality, and the second provides clear usage guidance. Every word earns its place with no redundancy or unnecessary elaboration.

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

Completeness5/5

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

Given the tool's simplicity (0 parameters, read-only operation, output schema exists), the description is complete. It explains what the tool returns, why to use it, and the scope of access (including subdirectories). With an output schema handling return values, no additional information about output format 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?

With 0 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since there are none, and instead focuses on the tool's purpose and usage context, which adds semantic value beyond the empty 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 clearly states the tool's purpose with a specific verb ('Returns') and resource ('list of directories that this server is allowed to access'), and distinguishes it from siblings by focusing on server permissions rather than file operations. It explicitly mentions what the tool does: returning accessible directories and their subdirectories.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Use this to understand which directories and their nested paths are available before trying to access files.' This directly addresses usage context and distinguishes it from siblings like list_directory or search_files by focusing on permission discovery rather than file listing.

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/modelcontextprotocol/filesystem'

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