Skip to main content
Glama

tr

Read-only

Translate or delete literal characters from input using character-by-character replacement. Supports deletion and squeezing repeats, outputting JSON or plain text.

Instructions

Translate or delete literal characters from files or stdin — character-by-character replacement (NO regex). Read-only, no side effects (reads input, writes to stdout). Use --delete to remove specific characters, --squeeze to collapse repeats. Returns JSON by default; use --raw for plain output. Use for simple character mapping. Not for regex-based substitution — use 'sed' externally. Not for column extraction — use 'cut'. See also 'cut', 'expand'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoWrite plain transformed text to stdout.
set1YesLiteral source/delete character set. GNU bracket/range syntax is not expanded.
set2NoLiteral replacement character set for translation.
inputNoInput text. When provided, takes priority over stdin and --path.
pathsNoInput file. Repeat for multiple files.
deleteNoDelete characters in SET1.
encodingNoText encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
max_linesNoMaximum JSON lines to emit.
show_encodingNoInclude encoding detection metadata in JSON result.
encoding_errorsNoHow to handle encoding errors (default: replace).replace
squeeze_repeatsNoSqueeze repeated output characters.
encoding_profileNoLocale-aware encoding fallback profile for auto-detection.
Behavior5/5

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

Description states 'Read-only, no side effects' which aligns with annotation readOnlyHint=true. It also clarifies default output format (JSON) and raw mode, adding useful context beyond annotations.

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?

Description is succinct (5 sentences), front-loaded with main purpose and key distinctions. No redundant information; each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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) and lack of output schema, the description covers essential behavioral traits, default behavior, and disqualifying use cases. Sibling context is rich, and description differentiates well.

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%, so baseline is 3. Description adds value by explaining the tool's character-level operation, default output, and brief flag purposes, though it does not detail all 12 parameters individually.

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?

Description explicitly states the tool translates or deletes literal characters from files or stdin with character-by-character replacement (no regex). It also distinguishes from sibling tools like sed and cut 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?

Provides clear usage guidance: 'Use --delete to remove specific characters, --squeeze to collapse repeats.' Explicitly states when not to use ('Not for regex-based substitution — use sed externally. Not for column extraction — use cut.') and references 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