Skip to main content
Glama

Expand delimited field to rows

bpj_table_explode_delimited
Read-onlyIdempotent

Split a text field on a literal delimiter and copy remaining fields into each child row.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rows": "<rows>",
      "column": "<column>",
      "delimiter": "<delimiter>"
    },
    "name": "bpj_table_explode_delimited"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes
delimiterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive read, so the bar is lower. The description does add real behavioral value by specifying the delimiter is literal (not a regex) and that non-target fields are duplicated into every child row, but it says nothing about empty segments, missing columns, or malformed record arrays.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the core transform and its row-copy side effect are stated immediately. It is efficient, though it terminates before error or edge-case handling could be noted.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, fully-required transform with no output schema and zero schema description coverage, the description covers the core operation but leaves the return shape (how child rows are ordered/identified) and failure modes undocumented. Adequate, but an agent would still have to guess at edge-case behavior.

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 description coverage is 0%, so the description must carry weight, and it partially does: 'text field' maps to column, 'literal delimiter' disambiguates delimiter semantics, and 'remaining fields' maps to rows. It still never explains that rows is a JSON record array string with a 12,000-character cap, nor that column must name an existing field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: split a text field on a delimiter and copy remaining fields into each child row. The one-row-to-many-rows transform is unambiguous and clearly distinct from neighboring table tools such as combine_fields or batches, though no sibling is named.

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

Usage Guidelines3/5

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

Usage is only implied by the mechanics: you would reach for this when a column holds multiple delimited values that should become separate rows. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. when to prefer a dedupe or coalesce tool instead).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.