Skip to main content
Glama
Wayazi

MCP File System

by Wayazi

read_multiple_files

Read content from multiple files simultaneously using the MCP File System. Input an array of file paths to retrieve data efficiently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYesArray of file paths to read

Implementation Reference

  • The handler function for the 'read_multiple_files' tool. It validates each file path, reads the contents using fs.readFile, handles individual file errors with Promise.allSettled, formats the output as text, and returns it in the expected MCP format.
    async ({ paths }: { paths: string[] }) => {
        const results = await Promise.allSettled(
            paths.map(async (filePath: string) => {
                try {
                    const validPath = validatePath(filePath);
                    const content = await fs.readFile(validPath, 'utf-8');
                    return { path: filePath, content, success: true };
                } catch (error: any) {
                    return { path: filePath, error: error.message, success: false };
                }
            })
        );
    
        const output = results.map(result => {
            if (result.status === 'fulfilled') {
                return `${result.value.path}: ${result.value.success ? 
                    result.value.content : `Error: ${result.value.error}`}`;
            }
            return `Error processing file: ${result.reason}`;
        }).join('\n\n');
    
        return { content: [{ type: 'text', text: output }] };
    }
  • The input schema for the 'read_multiple_files' tool, specifying an array of file paths.
    { paths: z.array(z.string()).describe("Array of file paths to read") },
  • src/index.ts:49-75 (registration)
    The registration of the 'read_multiple_files' tool using server.tool, including name, schema, and handler reference.
    server.tool(
        "read_multiple_files",
        { paths: z.array(z.string()).describe("Array of file paths to read") },
        async ({ paths }: { paths: string[] }) => {
            const results = await Promise.allSettled(
                paths.map(async (filePath: string) => {
                    try {
                        const validPath = validatePath(filePath);
                        const content = await fs.readFile(validPath, 'utf-8');
                        return { path: filePath, content, success: true };
                    } catch (error: any) {
                        return { path: filePath, error: error.message, success: false };
                    }
                })
            );
    
            const output = results.map(result => {
                if (result.status === 'fulfilled') {
                    return `${result.value.path}: ${result.value.success ? 
                        result.value.content : `Error: ${result.value.error}`}`;
                }
                return `Error processing file: ${result.reason}`;
            }).join('\n\n');
    
            return { content: [{ type: 'text', text: output }] };
        }
    );
  • Helper function validatePath used by the handler to ensure file paths are within allowed directories before reading.
    function validatePath(filePath: string): string {
        const absolutePath = path.resolve(filePath);
        if (!allowedDirs.some(dir => absolutePath.startsWith(path.resolve(dir)))) {
            throw new Error(`Access denied: ${filePath} is not within allowed directories`);
        }
        return absolutePath;
    }
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/Wayazi/mcp_file_system'

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