Skip to main content
Glama

csplit

Destructive

Split input at regex matches into separate files. Dry-run previews split points without writing, and overwrite protection prevents data loss.

Instructions

Split input into multiple files at regex match points with dry-run and overwrite protection. Destructive: creates output files on the filesystem. Use --dry_run to preview split points without creating files. Returns JSON with generated filenames and record counts. Use to partition data by content patterns. Not for fixed-size splitting — use 'split' for line-count or byte-size chunks. See also 'split'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFile to split, or '-' for stdin.
prefixNoOutput file prefix.xx
dry_runNoReport split outputs without writing files.
patternNoRegular expression; each match starts a new chunk.
encodingNoText encoding (default: utf-8). Use 'auto' for BOM/autodetection.utf-8
max_splitsNoMaximum regex matches to split at; 0 means all.
output_dirNoDirectory for split outputs..
show_encodingNoInclude encoding detection metadata in JSON result.
suffix_lengthNoNumeric suffix length.
allow_overwriteNoAllow replacing existing outputs.
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?

Discloses destructive nature (creates files) beyond annotation's destructiveHint. Adds dry-run, overwrite protection, and JSON return details. No contradiction with 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?

Four sentences, front-loaded with purpose and key warnings. Every sentence adds value (purpose, destructive warning, dry-run, JSON return, alternative). Efficient and no redundancy.

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?

For 12-parameter tool with no output schema, description covers purpose, behavior, dry-run, overwrite protection, and return format. Missing details like encoding handling but schema covers parameters fully. Minor gap for a complex tool.

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. Description mentions dry_run and allow_overwrite in context but doesn't add significant new meaning beyond schema descriptions.

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 splits input files at regex match points, with specific verb and resource. It distinguishes from sibling 'split' by explicitly noting fixed-size splitting is handled elsewhere.

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 explicit guidance: use for content-pattern partitioning, not for fixed-size; dry-run preview to avoid accidental file creation. Naming 'split' as alternative gives clear when-not-to-use.

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