Skip to main content
Glama

geezorg_read_file

Reads a line range from archived text files (.txt, .csv, .json, .tex, .xml) by path, offset, and limit so you can inspect specific content without loading whole files.

Instructions

Read lines [offset, offset+limit) of a text file in the archive (.txt/.csv/.json/.tex/.xml). Use geezorg_browse to find paths.

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": {
      "path": "<path>"
    },
    "name": "geezorg_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool reads rather than writes, specifies the line interval [offset, offset+limit), and lists supported text formats. However, it omits details such as encoding handling, out-of-range behavior, error responses, and whether access is restricted to archive files.

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 two tightly written sentences with no filler. The core operation is front-loaded, followed by the practical pointer to geezorg_browse.

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 three-parameter read tool with an output schema, the description supplies the essential call context: line-range semantics, supported file types, and how to obtain a path. It is mostly complete, though additional notes on offset bases and error behavior would strengthen it.

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 0%, so the description must compensate. It usefully explains that offset and limit define a line interval and that path points to a supported text file in the archive. It does not clarify whether offset is zero-based or describe defaults explicitly, though defaults appear in the schema.

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 states a specific verb and resource: 'Read lines ... of a text file in the archive.' It also scopes the operation to line ranges and named file extensions, making the tool's purpose immediately clear. The mention of 'geezorg_browse to find paths' distinguishes it from the path-discovery sibling.

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 gives a clear usage cue by naming geezorg_browse for finding paths before calling this tool. It does not explicitly state when not to use this tool or compare it to content-search alternatives, but the context is sufficient for a straightforward file-reading tool.

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