Skip to main content
Glama
zad0xlik

RateSpot MCP Server

by zad0xlik

list-directory

Retrieve directory contents by specifying a path; optionally list files recursively. Use this tool to efficiently manage and access directory structures on the RateSpot MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the directory to list
recursiveNoWhether to list files recursively

Implementation Reference

  • The handler function for the 'list-directory' tool. It reads the directory using fs.readdirSync, handles recursion if specified, uses FileAnalyzer.getFileInfo for each file, and returns a JSON array of file information.
      async (params) => {
        try {
          const files: ReturnType<typeof FileAnalyzer.getFileInfo>[] = [];
          const listFiles = (dir: string) => {
            const entries = fs.readdirSync(dir);
            for (const entry of entries) {
              const fullPath = path.join(dir, entry);
              const stats = fs.statSync(fullPath);
              if (stats.isFile()) {
                files.push(FileAnalyzer.getFileInfo(fullPath));
              } else if (stats.isDirectory() && params.recursive) {
                listFiles(fullPath);
              }
            }
          };
    
          listFiles(params.path);
          const fileInfos = files;
    
          return {
            content: [{
              type: "text",
              text: JSON.stringify(fileInfos, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error listing directory: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Zod input schema defining 'path' (required string) and 'recursive' (optional boolean, default false) parameters for the list-directory tool.
    {
      path: z.string().describe("Path to the directory to list"),
      recursive: z.boolean().optional().default(false).describe("Whether to list files recursively")
    },
  • MCP server tool registration call for 'list-directory', including name, schema, and handler reference.
    server.tool(
      "list-directory",
      {
        path: z.string().describe("Path to the directory to list"),
        recursive: z.boolean().optional().default(false).describe("Whether to list files recursively")
      },
      async (params) => {
        try {
          const files: ReturnType<typeof FileAnalyzer.getFileInfo>[] = [];
          const listFiles = (dir: string) => {
            const entries = fs.readdirSync(dir);
            for (const entry of entries) {
              const fullPath = path.join(dir, entry);
              const stats = fs.statSync(fullPath);
              if (stats.isFile()) {
                files.push(FileAnalyzer.getFileInfo(fullPath));
              } else if (stats.isDirectory() && params.recursive) {
                listFiles(fullPath);
              }
            }
          };
    
          listFiles(params.path);
          const fileInfos = files;
    
          return {
            content: [{
              type: "text",
              text: JSON.stringify(fileInfos, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error listing directory: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Supporting utility function called by the list-directory handler to retrieve detailed file metadata including size, MIME type, binary detection, and encoding for each file found.
    static getFileInfo(filePath: string) {
      const stats = fs.statSync(filePath);
      const ext = path.extname(filePath);
      const buffer = fs.readFileSync(filePath);
      
      // Detect MIME type
      let mimeType = this.getMimeTypeFromExtension(ext);
      if (fileType.fileTypes) {
        for (const [type, signature] of Object.entries(fileType.fileTypes)) {
          if (Array.isArray(signature) && 
              buffer.length >= signature.length &&
              signature.every((byte, i) => buffer[i] === byte)) {
            mimeType = `image/${type}`;
            break;
          }
        }
      }
    
      const isBinary = this.isBinaryFile(buffer);
      let encoding: string | undefined;
    
      // Try to detect encoding for text files
      if (!isBinary) {
        try {
          // Try UTF-8 first
          const content = buffer.toString('utf8');
          if (this.isValidUtf8(content)) {
            encoding = 'utf8';
          } else {
            // Try other common encodings
            const encodings = ['ascii', 'utf16le', 'latin1'];
            for (const enc of encodings) {
              try {
                iconv.decode(buffer, enc);
                encoding = enc;
                break;
              } catch {
                continue;
              }
            }
          }
        } catch {
          // If all encoding detection fails, default to binary
        }
      }
    
      return {
        path: filePath,
        size: stats.size,
        created: stats.birthtimeMs,
        modified: stats.mtimeMs,
        mimeType,
        extension: ext,
        isBinary,
        encoding
      };
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/zad0xlik/ratespot-mcp'

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