Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

read_file

Read-only

Reads a UTF-8 source file by line range and returns a SHA-256 concurrency token to support safe concurrent edits.

Instructions

Read a UTF-8 source file by line range, including a SHA-256 concurrency token.

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": {
      "file": "<file>"
    },
    "name": "read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesRelative file path
maxLinesNoNumber of lines, 1..600
startLineNoFirst line, 1-based

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description's real contribution is the UTF-8 encoding constraint, which usefully implies behavior on non-UTF-8 input. However, the trailing 'including a SHA-256 concurrency token' is never explained and does not correspond to any input parameter, adding confusion rather than behavioral clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that names verb, resource, and scoping mechanism with no filler. The closing clause about a SHA-256 concurrency token is cryptic and unearned by any schema field, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining returns — it should say how lines are returned and what happens at range boundaries or on truncation, and instead only hints at a token. For a three-parameter read tool with full schema coverage this is adequate but leaves real 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 description coverage is 100% — file, maxLines with its 1..600 bound, and startLine being 1-based are all documented in the schema. The description only echoes the line-range concept and adds a UTF-8 constraint, so it adds little meaning beyond the structured fields.

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?

States a specific verb and resource with scope: 'Read a UTF-8 source file by line range.' An agent can tell this is a partial-file reader rather than a full file writer or lister. It does not differentiate itself from the sibling 'read_files', so it stops short of a 5.

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?

Usage is only implied by 'by line range' — an agent can infer this is for paging through a file rather than grabbing all of it. There is no explicit when-to-use versus 'read_files', no note on when to omit startLine/maxLines, and no exclusions.

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