Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

read_files

Read-only

Reads up to 8 UTF-8 files from relative paths, capping each at 40 KB to gather context.

Instructions

Read up to 8 UTF-8 files, capped at 40 KB each for context gathering.

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": {
      "files": "<files>"
    },
    "name": "read_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesRelative file paths

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations' read-only and non-destructive safety profile, the description discloses UTF-8 handling and a 40 KB per-file cap. It does not clarify whether oversized or non-UTF-8 files are truncated, rejected, or produce errors.

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 single sentence is compact, front-loaded with the operation, and packed with relevant constraints. There is no redundant or promotional wording.

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 simple one-parameter read tool, the schema, annotations, and description together cover the input, safety profile, batch limit, encoding, and size limit. The absence of an output schema makes the missing return-format and cap/error behavior more noticeable, but these are modest gaps.

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 coverage is 100% and already documents that files contains one to eight relative paths, so the baseline is 3. The encoding and size constraints add file-eligibility context, but the description does not further explain path resolution or other input semantics.

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?

The description clearly states the verb and resource: reading multiple UTF-8 files for context gathering. The batch, encoding, and size details sharpen the purpose, but it does not distinguish this tool from the sibling read_file.

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?

"For context gathering" implies the intended scenario, and the eight-file limit suggests batch use. However, there is no explicit guidance on when to choose this over read_file or other context-gathering tools.

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