Sora Commander

Overview Schema Source Related Servers Discussions Admin

read_text_lines

Read exact numbered UTF-8 source lines for review from already-allowed paths by specifying a 1-based start line and bounded line count, without edits or permission changes.

Instructions

Read numbered UTF-8 source lines without creating a new grant.

Use when exact numbered source lines are needed for review. Choose 1-based start_line and a bounded max_lines; no edits or permission changes.

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": "read_text_lines"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Path to the target within the already-configured Owner read/edit roots; path alone grants no access.
`max_lines`	No	Maximum line count, 1 to 100; default 50.
`start_line`	No	First 1-based line to read (1 to 1000000); default 1.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does usefully declare that no new grant is created and that no edits or permission changes occur, implying a safe read. It does not disclose truncation behavior, what happens if start_line exceeds file length, or how the numbered output is shaped beyond the existence of an output schema.

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?

Three short sentences, front-loaded with the purpose and followed by the usage condition and parameter hint. Nothing is wasted, though the final clause slightly duplicates the read-only claim made in sentence one.

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?

An output schema exists and all three parameters are documented, so the description only needs to convey purpose, safety posture, and selection guidance, which it largely does. The main residual gap is differentiation from the other read_* siblings.

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 coverage is 100%, so path, max_lines, and start_line are already fully documented in the schema, including 1-based indexing and the 1-100 bound. The description's '1-based start_line and a bounded max_lines' merely restates that, adding no format or edge-case meaning.

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: read numbered UTF-8 source lines, plus the negative scope 'without creating a new grant.' It does not name which sibling to prefer over read_text_file, read_text_page, or read_text_chunk, so an agent must infer the distinction from 'numbered' alone.

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?

'Use when exact numbered source lines are needed for review' gives a clear triggering context. It stops short of exclusions or naming the alternative readers (read_text_file, read_text_page, read_text_chunk), so selection among the several read tools still requires inference.

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