Skip to main content
Glama

cut

Read-only

Select specific fields, characters, or bytes from each line. Extract columns from delimited data without side effects.

Instructions

Select specific fields, characters, or bytes from each input line. Read-only, no side effects. Returns JSON with the extracted columns by default; use --raw for plain text. Use to extract columns from tabular or delimited data. Not for replacing characters — use 'tr' for translation/deletion. Not for merging columns — use 'paste'. See also 'paste', 'tr'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoWrite plain transformed text to stdout.
bytesNo1-based byte ranges like '1,3-5'.
charsNo1-based character ranges like '1,3-5'.
pathsNoFiles to read, or '-' for stdin. Defaults to stdin.
fieldsNo1-based field ranges like '1,3-5'.
encodingNoText encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
delimiterNoField delimiter.
max_linesNoMaximum JSON lines to emit.
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.
output_delimiterNoDelimiter for selected fields.
Behavior4/5

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

The description adds value beyond the readOnlyHint annotation by disclosing default output format (JSON) and the --raw option for plain text. It also states 'Read-only, no side effects', which reinforces the annotation. No contradictions.

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 efficient and well-structured: 5 sentences, each serving a clear purpose. It front-loads the main action and then provides usage guidelines and exclusions. No redundant or unnecessary information.

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 the tool's complexity (12 parameters, no output schema), the description covers essential aspects: purpose, usage guidelines, output format, and behavioral traits. It does not duplicate schema details and provides enough context for correct invocation. Minor omission: could mention delimiter defaults, but schema already does.

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?

The input schema covers all 12 parameters with descriptions (100% coverage). The description does not add parameter-specific semantics but provides an overview. Baseline score of 3 is appropriate as the schema handles parameter details adequately.

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's purpose: 'Select specific fields, characters, or bytes from each input line.' It uses specific verbs and identifies the input resource, distinguishing it from siblings by explicitly stating what it is not for (replacing characters, merging columns) and naming alternatives 'tr' and 'paste'.

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?

The description explicitly says when to use ('extract columns from tabular or delimited data') and when not to use ('not for replacing characters', 'not for merging columns'), providing clear alternatives like 'tr' and 'paste'. It also directs to 'see also' for related tools.

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