csv-roundtrip
Will this CSV survive a typed round trip and a spreadsheet: leading zeros, big ids, dates, formulas, empty vs null — Parses CSV text (RFC 4180, caller dialect) against a column type map and reports, per cell with row, column, physical line and byte offset, everything that would change on a parse-serialize-parse round trip or when opened in Excel or Sheets: leading zeros stripped, integers beyond 2^53 or 15 significant digits, scientific-notation and date coercion ("1E5", "1-2", "MARCH1"), formula injection (= +
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": {
"text": "<text>"
},
"name": "csv-roundtrip"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | CSV text, up to 200000 characters. | |
| types | No | Object mapping column name to one of string, identifier, integer, decimal, boolean, date, datetime (max 200). Unlisted columns are "string". Use "identifier" for digit strings that must keep leading zeros. | |
| dialect | No | ||
| nullToken | No | Text that means null (e.g. "NULL", "\\N"). Default: none, so only an unquoted empty field is null. | |
| spreadsheet | No | Check Excel/Sheets coercion hazards (default true). |