Skip to main content
Glama

read_file

Read the contents of a file by specifying its path, with optional start and end lines to limit the output to a range.

Instructions

Read the contents of a file. Optionally specify a line range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFile path (absolute or relative to workspace root)
start_lineNoFirst line to read (1-indexed, inclusive)
end_lineNoLast line to read (1-indexed, inclusive)
workspace_rootNoWorkspace root directory (optional)

Implementation Reference

  • src/index.ts:167-180 (registration)
    Tool registration with name 'read_file', description, and JSON Schema input definition requiring 'path' and accepting optional 'start_line', 'end_line', and 'workspace_root'.
    {
      name: "read_file",
      description: "Read the contents of a file. Optionally specify a line range.",
      inputSchema: {
        type: "object",
        properties: {
          path: { type: "string", description: "File path (absolute or relative to workspace root)" },
          start_line: { type: "number", description: "First line to read (1-indexed, inclusive)" },
          end_line: { type: "number", description: "Last line to read (1-indexed, inclusive)" },
          workspace_root: { type: "string", description: "Workspace root directory (optional)" },
        },
        required: ["path"],
      },
    },
  • Handler that resolves the file path, calls readFileLines with optional line range, and returns text content result.
    case "read_file": {
      const filePath = resolveWorkspacePath(a.path as string, a.workspace_root as string | undefined);
      const content = await readFileLines(
        filePath,
        a.start_line as number | undefined,
        a.end_line as number | undefined
      );
      return { content: [{ type: "text", text: content }] };
    }
  • Helper function that reads a file. If no line range given, reads entire file via fs/promises readFile. Otherwise streams the file line-by-line and returns only the requested lines.
    async function readFileLines(
      filePath: string,
      startLine?: number,
      endLine?: number
    ): Promise<string> {
      if (startLine === undefined && endLine === undefined) {
        return readFile(filePath, "utf-8");
      }
      const lines: string[] = [];
      const rl = createInterface({ input: createReadStream(filePath), crlfDelay: Infinity });
      let lineNum = 1;
      for await (const line of rl) {
        if (startLine === undefined || lineNum >= startLine) {
          if (endLine === undefined || lineNum <= endLine) lines.push(line);
          else break;
        }
        lineNum++;
      }
      return lines.join("\n");
    }
  • Helper that resolves a potentially relative file path against a workspace root (or cwd). Absolute paths are returned as-is.
    function resolveWorkspacePath(filePath: string, workspaceRoot?: string): string {
      if (filePath.startsWith("/") || /^[A-Za-z]:/.test(filePath)) return filePath;
      const base = workspaceRoot ?? process.cwd();
      return resolve(join(base, filePath));
    }
Behavior2/5

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

With no annotations, description should disclose behavioral traits. Does not state that it does not modify files, what happens on missing file, or that it returns raw content. Only mentions line range option.

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?

Single sentence with no fluff. Front-loaded information. Could be slightly more informative but still efficient.

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

Completeness2/5

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

No output schema, so description should mention return value (file contents as string). Does not specify behavior for line range or what happens if path is invalid.

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 has 100% description coverage for all parameters. Description adds no additional semantics beyond the schema, achieving baseline score.

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?

Clearly states the verb 'Read' and the resource 'contents of a file'. Distinguishes from siblings like write_file, edit_file, and delete_path which have different actions.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., search_files for content search, get_file_info for metadata). Does not mention that it is read-only or safe.

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/KloutDevs/vscode-mcp'

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