Skip to main content
Glama

listAllowedDirectories

Lists directories accessible for file operations within the Pinata MCP server, enabling users to identify available storage locations for IPFS content management.

Instructions

List all directories that this MCP server is allowed to access for file operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration and handler implementation for listAllowedDirectories - lists directories the MCP server is allowed to access for file operations. Returns either command-line specified directories or the current working directory as default.
    server.tool(
      "listAllowedDirectories",
      "List all directories that this MCP server is allowed to access for file operations",
      {},
      async () => {
        const dirs =
          allowedDirectories.length > 0
            ? allowedDirectories
            : [normalizePath(process.cwd())];
        return {
          content: [
            {
              type: "text",
              text: `Allowed directories:\n${dirs.join("\n")}`,
            },
          ],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists directories but doesn't describe return format, pagination, error conditions, or whether it's a read-only operation. This leaves significant gaps for a tool that likely involves system-level access.

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 efficiently conveys the core purpose without wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, directory paths), access permissions implications, or error handling for a tool dealing with server access permissions.

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 no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary 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 verb ('List') and resource ('directories'), specifying that these are directories the MCP server can access for file operations. It distinguishes from siblings by focusing on directory permissions rather than file operations, though it doesn't explicitly contrast with specific sibling tools.

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. The description doesn't mention prerequisites, timing, or comparison to other tools like 'listGroups' or 'searchFiles', leaving the agent to infer usage context.

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/PinataCloud/pinata-mcp'

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