Skip to main content
Glama
Sign In
fs-mcp-server

fs-mcp-server

by qsrahman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read Multiple Files

read_multiple_files
Read-onlyIdempotent

Read the contents of multiple files at once, returning each path with its content while continuing if an individual read fails.

Instructions

Read the contents of multiple files simultaneously. Each file's content is returned with its path as a reference. A failed read of one file does not stop the others. Output is capped at about 200,000 characters in total; a file that does not fit is cut, with the offset to continue from with read_file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paths": "<paths>"
    },
    "name": "read_multiple_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesPaths of the files to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: per-file failure isolation (one bad path does not abort the batch) and a ~200,000-character total output cap with truncation and a continuation offset. That is real value beyond the structured fields, though it omits the 50-file ceiling and any ordering guarantee for results.

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?

Four short sentences, front-loaded with the core action, then return shape, then failure semantics, then the size limit with the recovery path. No sentence is redundant and the constraint-plus-remedy pairing is efficient.

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 one-parameter batch read with annotations and no output schema, the description covers what comes back (content keyed by path), what happens on partial failure, and what happens at the size boundary. Only the 50-file cap and result ordering are left solely to the schema, which is a minor gap.

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?

There is a single parameter and schema description coverage is 100%, so the schema already carries the semantics of "paths." The description does not add meaning about path format, ordering, or the maxItems of 50, so the baseline of 3 applies.

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?

"Read the contents of multiple files simultaneously" gives a specific verb plus resource and, through "multiple," implicitly contrasts with the single-file read_file sibling. It stops short of naming read_file as the single-file alternative up front, but the resource and scope are unambiguous.

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

Usage Guidelines3/5

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

The batching intent is implied by "multiple files simultaneously," but the description never states the selection rule (use this for two or more files, use read_file for one). read_file is only referenced reactively, as the way to resume a truncated file, not as a usage alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools