Skip to main content
Glama

fold

Read-only

Wrap long input lines at a fixed character width for display-constrained formatting. Breaks lines at exact positions, adapting to terminal width constraints.

Instructions

Wrap long input lines at a fixed character width, breaking at exact positions. Read-only, no side effects. Returns JSON with wrapped text by default; use --raw for plain output. Use for display-constrained formatting or terminal-width adaptation. Not for paragraph-aware reflowing — use 'fmt' to preserve paragraph structure. See also 'fmt'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoWrite folded text without a JSON envelope.
pathsNoFiles to fold, or '-' for stdin. Defaults to stdin.
widthNoMaximum line width.
encodingNoText encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
max_linesNoMaximum JSON lines to emit.
break_wordsNoBreak words longer than the width.
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 explicitly states 'Read-only, no side effects', which is consistent with the readOnlyHint annotation. It also discloses default output format (JSON) and the availability of raw output via --raw, adding 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?

The description is extremely concise with two sentences plus a usage note, packing essential information without waste.

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 9 parameters and no output schema, the description covers core purpose, usage context, and output format. It could be slightly more complete by mentioning encoding fallbacks, but overall it is adequate.

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% with detailed parameter descriptions. The description adds minimal extra meaning beyond mentioning the 'raw' flag behavior and the default width, so a baseline score of 3 is appropriate.

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 wraps long input lines at a fixed width, and explicitly distinguishes itself from the sibling 'fmt' by noting it does not do paragraph-aware reflowing.

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 provides explicit when-to-use (display-constrained formatting, terminal-width adaptation) and when-not-to-use (not for paragraph reflowing), and names the alternative tool 'fmt'.

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