Skip to main content
Glama
Sign In
checkpointer

checkpointer

by IronKommander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read a file inside the project directory.

read_file
Read-only

Read a file's contents with line numbers. Specify start and end lines to view specific sections without truncation.

Instructions

To read the contents of a file with line numbers. Returns numbered lines. For large files, output is truncated to head+tail unless a specific range is given via start_line/end_line (1-based, inclusive).

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

Input Schema

NameRequiredDescriptionDefault
end_lineNo
filepathYes
start_lineNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark as read-only and non-destructive. The description adds value by explaining truncation and range parameters (start_line/end_line), which are not inferable from annotations.

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?

Two sentences, no filler. Purpose is front-loaded, each sentence adds essential information. Highly concise.

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

Completeness5/5

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

Given the simple read operation and existence of output schema, the description covers truncation and range usage completely. No gaps for typical usage.

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?

No parameter descriptions in schema (0% coverage). Description explains start_line/end_line as 1-based inclusive, and filepath is implied. Compensates partially but not fully for missing schema docs.

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 verb 'read' and resource 'file with line numbers' are clearly stated. It distinguishes from siblings like write_file and edit_file_lines by specifying the read-only nature and line numbering.

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?

Describes when to use (reading file contents with line numbers) and mentions truncation behavior for large files. Lacks explicit alternatives or when-not conditions, but context is clear.

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