Skip to main content
Glama
MausRundung

Project Explorer MCP Server

by MausRundung

list_allowed_directories

Check which directories the Project Explorer MCP Server can access to understand available exploration paths before using other tools.

Instructions

Returns the list of directories that this MCP server is allowed to access. This is useful for understanding which directories can be explored or searched before attempting to use other tools. The allowed directories are configured when the server starts and cannot be modified at runtime.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that constructs and returns a markdown-formatted list of allowed directories as MCP tool response content.
    export async function handleListAllowed(args: any, allowedDirectories: string[]) {
      let result = "# Allowed Directories\n\n";
      
      if (allowedDirectories.length === 0) {
        result += "No directories are currently allowed.";
      } else {
        result += `This MCP server has access to ${allowedDirectories.length} director${allowedDirectories.length === 1 ? 'y' : 'ies'}:\n\n`;
        
        allowedDirectories.forEach((dir, index) => {
          result += `${index + 1}. ${dir}\n`;
        });
        
        result += "\nYou can use these directories with other tools like explore_project, search_files, etc.";
      }
      
      return {
        content: [
          {
            type: "text",
            text: result
          }
        ]
      };
    }
  • The tool object definition including name, description, and empty input schema (no parameters required).
    export const listAllowedTool = {
      name: "list_allowed_directories",
      description: "Returns the list of directories that this MCP server is allowed to access. This is useful for understanding which directories can be explored or searched before attempting to use other tools. The allowed directories are configured when the server starts and cannot be modified at runtime.",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    };
  • src/index.ts:53-54 (registration)
    Switch case in the CallToolRequestSchema handler that routes execution to the list_allowed_directories handler function.
    case "list_allowed_directories":
      return await handleListAllowed(args, ALLOWED_DIRECTORIES);
  • src/index.ts:34-43 (registration)
    Inclusion of the listAllowedTool in the response to ListToolsRequestSchema, registering it for discovery.
    return {
      tools: [
        exploreProjectTool,
        listAllowedTool,
        searchTool,
        renameFileTool,
        deleteFileTool,
        checkOutdatedTool
      ]
    };
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a read-only operation ('Returns'), reveals the data source ('configured when the server starts'), and states immutability ('cannot be modified at runtime'). It doesn't cover potential errors or response format, but provides substantial 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 perfectly front-loaded with the core purpose in the first sentence, followed by usage guidance and behavioral details. Every sentence earns its place: the first defines the tool, the second explains when to use it, and the third provides important behavioral context about configuration immutability.

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

Completeness4/5

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

For a zero-parameter tool with no annotations or output schema, the description provides excellent context about what the tool does, when to use it, and key behavioral constraints. The only gap is lack of information about return format (e.g., array of paths, structured objects), but given the tool's simplicity, this is a minor omission.

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 coverage, the baseline would be 4. The description appropriately explains why there are no parameters ('The allowed directories are configured when the server starts'), adding meaningful context about the parameterless nature rather than just stating it takes no inputs.

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 specific action ('Returns the list of directories') and resource ('directories that this MCP server is allowed to access'), distinguishing it from siblings like 'explore_project' or 'search_files' which operate on files rather than server configuration. It explicitly defines the tool's scope as retrieving server access permissions.

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 ('useful for understanding which directories can be explored or searched before attempting to use other tools'), effectively positioning it as a prerequisite discovery tool. It distinguishes from siblings by focusing on server configuration rather than file operations.

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/MausRundung/mcp-explorer'

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