Skip to main content
Glama

ParecodeExpand

Read a specific line range from a file with optional context padding, following a code search match. Returns estimated token count to manage context budget.

Instructions

Read a specific line range of a file — the natural follow-up to a ParecodeSearch match or an omittedLineRanges entry it returned. Use instead of a full-file Read (or Read with offset/limit) when you already know roughly where the code lives and just need more lines around it. Give the known (file, startLine, endLine) and optionally pad with contextBefore/contextAfter; out-of-range lines are clamped silently and the returned lineRange reflects the actual slice. Reports estimatedTokens in the same form as ParecodeSearch so you can budget before consuming. Read-only — to change code use ParecodeEdit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPath to the file to read (typically the `file` from a ParecodeSearch match).
startLineYesStarting line (1-based, inclusive)
endLineYesEnding line (1-based, inclusive)
contextBeforeNoAdditional lines to include before startLine. Default 0.
contextAfterNoAdditional lines to include after endLine. Default 0.
Behavior5/5

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

No annotations provided; description fully covers behaviors: silent clamping of out-of-range lines, returned lineRange reflects actual slice, reports estimatedTokens, and read-only nature.

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?

Concise two-sentence description that is front-loaded with purpose and efficiently covers all key aspects without redundancy.

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?

No output schema, but description mentions returned values (lineRange, estimatedTokens) and behavior. Could be slightly more detailed on return structure, but sufficient given simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds context above schema by explaining how parameters relate to search matches and padding behavior, though some parameter details are already clear from 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 clearly states the tool reads a specific line range of a file and positions it as a follow-up to ParecodeSearch, distinguishing it from siblings like ParecodeEdit and full-file reads.

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

Usage Guidelines5/5

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

Explicitly specifies when to use (as follow-up to ParecodeSearch) and when not (instead of full-file Read), and mentions alternative ParecodeEdit for changes.

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/BasilSkyWalk/parecode'

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