OnlineCyberTools MCP (280+ filterable tools)

text_text_column

Read-onlyIdempotent

Extract, align, or analyze columns from delimited text. Use extract to pull a single column, align to format into a monospaced table, or split for a per-column analysis report.

Instructions

Extract, Align, or Analyze Columns in Delimited Text. Splits each line of delimited text on a delimiter and operates on the resulting columns. operation=extract pulls one 1-based column into a newline-separated list; operation=align pads every column to a fixed width (left/right/center) for monospaced tabular output; operation=split emits a human-readable per-column analysis report grouping values by column. Use this for columnar/tabular text (CSV, TSV, space-separated logs) when you need a single column or aligned table; use text_splitter to break text into rows/tokens (lines, regex, fixed length), text_joiner to recombine fields, and csv_json for structured CSV->JSON. Read-only, non-destructive pure computation that runs in-process with no network or storage; rate limited to 60 req/min (anonymous) / 120 req/min (authenticated). Returns the processed text plus before/after line/character/word stats and the resolved options.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Multi-line delimited input; each line is split on the delimiter into columns.
`operation`	No	Column operation to perform.	extract
`columnNumber`	No	1-based column index used by the extract operation; clamped to a minimum of 1.
`delimiter`	No	Field separator splitting each line into columns; must be non-empty.
`alignment`	No	Padding direction for the align operation.	left
`width`	No	Target column width in characters for the align operation; clamped to 1-200.
`fillChar`	No	Single character used to pad columns during align; first character is used, empty falls back to a space.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when the operation succeeded.
`result`	No	Processed text: extracted column list, aligned table, or analysis report.
`stats`	No	Before/after metrics plus operation-specific counters.
`options`	No	Echo of the resolved (normalized) request parameters.

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / alignment / default
```
Added value: +"left"
```

addedInput schema / properties / alignment / description

Added value: +"Padding direction for the align operation."

addedInput schema / properties / alignment / enum

Added value: +[
+  "left",
+  "right",
+  "center"
+]

addedInput schema / properties / columnNumber / default
```
Added value: +1
```

addedInput schema / properties / columnNumber / description

Added value: +"1-based column index used by the extract operation; clamped to a minimum of 1."

addedInput schema / properties / columnNumber / minimum
```
Added value: +1
```
addedInput schema / properties / delimiter / default
```
Added value: +" "
```

addedInput schema / properties / delimiter / description

Added value: +"Field separator splitting each line into columns; must be non-empty."

addedInput schema / properties / fillChar / default
```
Added value: +" "
```

addedInput schema / properties / fillChar / description

Added value: +"Single character used to pad columns during align; first character is used, empty falls back to a space."

addedInput schema / properties / operation / default
```
Added value: +"extract"
```
addedInput schema / properties / operation / description
```
Added value: +"Column operation to perform."
```

addedInput schema / properties / operation / enum

Added value: +[
+  "extract",
+  "align",
+  "split"
+]

addedInput schema / properties / text / description

Added value: +"Multi-line delimited input; each line is split on the delimiter into columns."

addedInput schema / properties / width / default
```
Added value: +20
```

addedInput schema / properties / width / description

Added value: +"Target column width in characters for the align operation; clamped to 1-200."

addedInput schema / properties / width / maximum
```
Added value: +200
```
addedInput schema / properties / width / minimum
```
Added value: +1
```

changedInput schema / required

Previous value: -[
-  "text",
-  "operation",
-  "columnNumber",
-  "delimiter",
-  "alignment",
-  "width",
-  "fillChar"
-]New value: +[
+  "text"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "options": {
+      "description": "Echo of the resolved (normalized) request parameters.",
+      "properties": {
+        "alignment": {
+          "description": "Resolved alignment.",
+          "type": "string"
+        },
+        "columnNumber": {
+          "description": "Resolved 1-based column index.",
+          "type": "integer"
+        },
+        "delimiter": {
+          "description": "Resolved delimiter.",
+          "type": "string"
+        },
+        "fillChar": {
+          "description": "Resolved fill character.",
+          "type": "string"
+        },
+        "operation": {
+          "description": "Operation performed.",
+          "type": "string"
+        },
+        "width": {
+          "description": "Resolved column width.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "result": {
+      "description": "Processed text: extracted column list, aligned table, or analysis report.",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Before/after metrics plus operation-specific counters.",
+      "properties": {
+        "operation": {
+          "description": "Operation-specific counters (e.g. extractedCount, maxColumns, processedLines, extractionRate).",
+          "type": "object"
+        },
+        "original": {
+          "description": "Statistics for the input text.",
+          "properties": {
+            "averageWordsPerLine": {
+              "description": "Mean words per line.",
+              "type": "number"
+            },
+            "characters": {
+              "description": "Character count.",
+              "type": "integer"
+            },
+            "lines": {
+              "description": "Line count.",
+              "type": "integer"
+            },
+            "words": {
+              "description": "Alphabetic word count.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "result": {
+          "description": "Statistics for the output text (same fields as original).",
+          "properties": {
+            "averageWordsPerLine": {
+              "description": "Mean words per line.",
+              "type": "number"
+            },
+            "characters": {
+              "description": "Character count.",
+              "type": "integer"
+            },
+            "lines": {
+              "description": "Line count.",
+              "type": "integer"
+            },
+            "words": {
+              "description": "Alphabetic word count.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the operation succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds critical behavioral context: 'Read-only, non-destructive pure computation that runs in-process with no network or storage; rate limited to 60 req/min (anonymous) / 120 req/min (authenticated). Returns the processed text plus before/after line/character/word stats and the resolved options.' No contradictions.

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 thorough yet efficient: a single, well-structured paragraph. It front-loads the purpose, then explains operations, usage conditions, and technical details. Every sentence earns its place with no redundancy.

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 (7 parameters, multiple operations, existing output schema), the description covers all necessary aspects: operations, usage context, behavioral traits, rate limits, and return values. The output schema provides the return format, so the description does not need to repeat it.

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. The description briefly ties operations to parameters (e.g., columnNumber for extract) but does not add substantial meaning beyond the schema definitions. It's adequate but not exceptional.

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 starts with a clear verb+resource: 'Extract, Align, or Analyze Columns in Delimited Text.' It explicitly lists three operations and distinguishes the tool from siblings like text_splitter, text_joiner, and csv_json, leaving no ambiguity about what the tool does.

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 guidance: 'Use this for columnar/tabular text (CSV, TSV, space-separated logs) when you need a single column or aligned table.' It also names alternatives for other use cases, making it clear when not to use this tool.

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

Deploy Server