Skip to main content
Glama
A-Niranjan

MCP Filesystem Server

by A-Niranjan

read_multiple_files

Read contents from multiple files simultaneously for efficient analysis or comparison. Returns each file's content with its path, continues operation even if individual reads fail, and works within allowed directories.

Instructions

Read the contents of multiple files simultaneously. This is more efficient than reading files one by one when you need to analyze or compare multiple files. Each file's content is returned with its path as a reference. Failed reads for individual files won't stop the entire operation. Only works within allowed directories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYesList of file paths to read
encodingNoFile encodingutf-8

Implementation Reference

  • Core handler function that implements the read_multiple_files tool logic: reads multiple files concurrently with path validation, size checks, and per-file error handling.
    export async function readMultipleFiles(
      args: z.infer<typeof ReadMultipleFilesArgsSchema>,
      config: Config
    ): Promise<Record<string, string | Error>> {
      const endMetric = metrics.startOperation('read_multiple_files')
      const results: Record<string, string | Error> = {}
    
      await Promise.all(
        args.paths.map(async (filePath: string) => {
          try {
            const validPath = await validatePath(filePath, config)
    
            // Validate file size
            if (config.security.maxFileSize > 0) {
              await validateFileSize(validPath, config.security.maxFileSize)
            }
    
            const content = await fs.readFile(validPath, args.encoding)
            results[filePath] = content
          } catch (error) {
            if (error instanceof Error) {
              results[filePath] = error
            } else {
              results[filePath] = new Error(String(error))
            }
          }
        })
      )
    
      endMetric()
      return results
    }
  • Zod schema for validating input arguments to the read_multiple_files tool: requires an array of file paths and optional encoding.
    export const ReadMultipleFilesArgsSchema = z.object({
      paths: z.array(z.string()).describe('List of file paths to read'),
      encoding: z
        .enum(['utf-8', 'utf8', 'base64'])
        .optional()
        .default('utf-8')
        .describe('File encoding'),
    })
  • src/index.ts:244-253 (registration)
    Registration of the read_multiple_files tool in the ListTools response, including name, description, and derived JSON schema.
    {
      name: 'read_multiple_files',
      description:
        'Read the contents of multiple files simultaneously. This is more ' +
        'efficient than reading files one by one when you need to analyze ' +
        "or compare multiple files. Each file's content is returned with its " +
        "path as a reference. Failed reads for individual files won't stop " +
        'the entire operation. Only works within allowed directories.',
      inputSchema: zodToJsonSchema(ReadMultipleFilesArgsSchema) as ToolInput,
    },
  • MCP server dispatcher case for read_multiple_files: parses arguments, calls the core handler, formats results with error handling, and returns MCP content response.
    case 'read_multiple_files': {
      const parsed = ReadMultipleFilesArgsSchema.safeParse(a)
      if (!parsed.success) {
        throw new FileSystemError(`Invalid arguments for ${name}`, 'INVALID_ARGS', undefined, {
          errors: parsed.error.format(),
        })
      }
    
      const results = await readMultipleFiles(parsed.data, config)
      const formattedResults = Object.entries(results)
        .map(([filePath, content]) => {
          if (content instanceof Error) {
            return `${filePath}: Error - ${content.message}`
          }
          return `${filePath}:\n${content}\n`
        })
        .join('\n---\n')
    
      endMetric()
      return {
        content: [{ type: 'text', text: formattedResults }],
      }
    }
Behavior4/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 effectively describes key behavioral traits: partial failure tolerance ('Failed reads for individual files won't stop the entire operation'), security constraints ('Only works within allowed directories'), and the return format ('Each file's content is returned with its path as a reference'). It doesn't mention performance characteristics like rate limits or detailed error handling.

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 four sentences that each earn their place: states the core functionality, explains efficiency benefit, describes return format, and specifies constraints. It's front-loaded with the main purpose and wastes no words.

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?

Given the tool's moderate complexity (batch file reading with partial failure tolerance), no annotations, and no output schema, the description does well but has minor gaps. It explains the operation, constraints, and return format adequately, but doesn't detail error responses or performance characteristics that would be helpful for a batch operation tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents both parameters. The description doesn't add any parameter-specific information beyond what's in the schema (paths array, encoding options). The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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 ('Read the contents of multiple files simultaneously'), distinguishes it from the sibling 'read_file' tool by emphasizing batch efficiency, and explicitly mentions the resource ('files'). It provides a precise verb+resource combination with clear differentiation from alternatives.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('more efficient than reading files one by one when you need to analyze or compare multiple files') and mentions a constraint ('Only works within allowed directories'). However, it doesn't explicitly state when NOT to use it or name specific alternative tools like 'read_file' for single-file scenarios.

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/A-Niranjan/mcp-filesystem'

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