Skip to main content
Glama

nl

Read-only

Number lines from files or stdin with configurable alignment, delimiter, and starting number. Outputs JSON or plain text for reference or debugging.

Instructions

Number input lines with configurable formatting (alignment, delimiter, starting number). Read-only, no side effects. Returns JSON with numbered lines by default; use --raw for plain text. Use to add line numbers for reference or debugging. Not for simple concatenation — use 'cat'. See also 'cat'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoWrite numbered text without a JSON envelope.
pathsNoFiles to number, or '-' for stdin. Defaults to stdin.
startNoStarting line number.
widthNoMinimum number width.
encodingNoText encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
incrementNoLine number increment.
max_linesNoMaximum JSON records to emit.
separatorNoSeparator between number and line.
number_blankNoAlso number blank lines.
show_encodingNoInclude encoding detection metadata in JSON result.
encoding_errorsNoHow to handle encoding errors (default: replace).replace
encoding_profileNoLocale-aware encoding fallback profile for auto-detection.
Behavior5/5

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

The description adds behavioral context beyond annotations: it states read-only nature (consistent with readOnlyHint), explains default output format (JSON) and the --raw flag, and confirms no side effects.

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?

Three concise sentences, front-loaded with purpose, no fluff. Every sentence adds value.

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?

Given 12 parameters fully described in schema and no output schema, the description covers return format and key behavior. Could elaborate on handling multiple files or the exact JSON structure, but overall sufficient.

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 baseline is 3. The description mentions configurable formatting (alignment, delimiter, starting number) but adds minimal new meaning beyond what the schema already documents.

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 numbers input lines with configurable formatting, and distinguishes it from 'cat' explicitly, which is a sibling tool.

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?

Provides specific use cases (adding line numbers for reference or debugging), a clear exclusion (not for simple concatenation), and an explicit alternative ('cat').

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/caseSHY/AI-CLI'

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