Skip to main content
Glama
Sign In
@qelos/better-mcp

@qelos/better-mcp

by qelos-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fs__read_multiple_files

Read multiple files simultaneously to analyze or compare content efficiently. Returns each file's content with its path, continuing even if some files fail.

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.

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": "fs__read_multiple_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesArray of file paths to read. Each path must be a string pointing to a valid file within allowed directories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses key behaviors: failure tolerance ('Failed reads... won't stop the entire operation'), return structure ('Each file's content is returned with its path'), and permission constraint ('Only works within allowed directories'). It lacks details on concurrency or max file limits but is otherwise transparent.

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 four sentences, front-loaded with the primary action, and each sentence adds distinct value: purpose, efficiency, return format, failure handling, and constraint. No repetition or unnecessary 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 no output schema, the description adequately covers the output format and error handling. It provides usage context and constraints. However, it misses potential limits (max files, max size) and whether reading is sequential or parallel, which would improve completeness.

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% as the input schema fully describes the 'paths' parameter. The tool description does not add new parameter-level semantics beyond reiterating 'allowed directories' and failure handling. Per guidelines, baseline is 3.

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 it reads multiple files simultaneously, highlights efficiency for analyzing/comparing multiple files, and distinguishes itself from sibling tools like fs__read_file which read single files. The verb 'read' and resource 'multiple files' are specific.

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 explains it is more efficient than reading files one by one and that failed reads won't stop the operation, guiding agents to use it when handling multiple files or tolerance for failures. However, it does not explicitly state when not to use it (e.g., for single file use fs__read_file).

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