Skip to main content
Glama

sort

Read-only

Sort text lines from files or stdin with options for numeric, reverse, and unique ordering. Returns sorted lines for downstream processing.

Instructions

Sort text lines deterministically from files or stdin. Read-only, no side effects. Use --numeric for numerical sort, --reverse for descending order, --unique to remove duplicates, and --seed for deterministic tie-breaking. Returns JSON with sorted lines by default; use --raw for plain output. Use to order data for downstream processing. Not for deduplication of non-sorted data — pipe to 'uniq' for adjacent dedup. Not for randomizing — use 'shuf'. See also 'uniq', 'shuf'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoWrite plain transformed text to stdout.
checkNoCheck whether input is sorted; exit non-zero if not.
pathsNoFiles to sort, or '-' for stdin. Defaults to stdin.
stableNoStable sort: preserve relative order of equal keys.
uniqueNoEmit only the first of equal sorted lines.
numericNoSort by the first numeric token.
reverseNoReverse the sort order.
encodingNoText encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
max_linesNoMaximum JSON lines to emit.
ignore_caseNoCompare case-insensitively.
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 states 'Read-only, no side effects,' aligning with the readOnlyHint annotation, and adds context about deterministic sorting, tie-breaking, and output format.

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 concise, front-loaded with the main purpose, followed by flag details, then limitations and alternatives; every sentence serves a purpose.

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 13 parameters and no output schema, the description covers core functionality (sorting, output format, key flags) and notes encoding via schema, but could mention encoding parameters more explicitly; still adequate for agent decision-making.

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?

The schema provides full parameter descriptions (100% coverage), but the description adds a high-level summary and groups related flags (--numeric, --reverse, --unique), aiding quick understanding despite not adding many new specifics.

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 it sorts text lines deterministically from files or stdin, and distinguishes it from sibling tools like uniq and shuf by specifying what it does not do.

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 provides when to use (order data for downstream processing), when not to use (not for deduplication of non-sorted data, not for randomizing), and names alternatives (uniq, shuf).

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