Skip to main content
Glama

split_column

Split column values by delimiter to extract specific parts or expand into multiple columns for CSV data transformation.

Instructions

Split column values by delimiter.

Returns: ColumnOperationResult with split details

Examples: # Keep first part of split split_column(ctx, "full_name", " ", part_index=0)

# Keep last part
split_column(ctx, "email", "@", part_index=1)

# Expand into multiple columns
split_column(ctx, "address", ",", expand_to_columns=True)

# Expand with custom column names
split_column(ctx, "name", " ", expand_to_columns=True,
            new_columns=["first_name", "last_name"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
columnYesColumn name to split values in
delimiterNoString delimiter to split on
part_indexYesWhich part to keep (0-based index, None for first part)
expand_to_columnsYesWhether to expand splits into multiple columns
new_columnsYesNames for new columns when expanding

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether operation completed successfully
operationYesType of operation performed
transformNoTransform description
part_indexNoPart index for split operations
nulls_filledNoNumber of null values filled
rows_removedNoNumber of rows removed (for remove_duplicates)
rows_affectedYesNumber of rows affected by operation
values_filledNoNumber of values filled (for fill_missing_values)
updated_sampleNoSample values after operation
original_sampleNoSample values before operation
columns_affectedYesNames of columns affected
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the operation and return type ('ColumnOperationResult with split details'), but doesn't mention important behavioral aspects like whether this modifies data in-place, requires specific permissions, or has performance implications for large datasets.

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 perfectly structured with a clear purpose statement, return value information, and multiple practical examples that demonstrate different usage patterns. Every sentence serves a specific purpose with zero wasted words.

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 moderate complexity, 100% schema coverage, and presence of an output schema, the description is quite complete. It explains the operation, shows multiple usage patterns, and mentions the return type. The main gap is lack of behavioral context about data modification implications.

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 schema has 100% description coverage, so the baseline is 3. The description adds value through examples that illustrate how parameters interact (e.g., 'part_index' vs 'expand_to_columns'), but doesn't provide additional semantic context beyond what's already documented in the 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's purpose with a specific verb ('split') and resource ('column values'), and it distinguishes itself from siblings like 'extract_from_column' or 'transform_column_case' by focusing specifically on delimiter-based splitting operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context through examples showing when to use different parameter combinations (keeping first/last part, expanding to multiple columns), but doesn't explicitly state when NOT to use this tool or name specific alternatives among the many sibling tools available.

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/jonpspri/databeak'

If you have feedback or need assistance with the MCP directory API, please join our Discord server