Tokenrip

Create table from CSV

table_create_from_csv

Create a table and rows from CSV. headers and explicit schema are mutually exclusive; a column name is 1 to 256 characters with no leading or trailing space, comma or square bracket (headers are trimmed), and an unclosed quote is INVALID_INPUT. A schema may mark at most one column unique, the key. A key value repeated in the file (two blank cells count) is STATE_CONFLICT, and a key value over 1024 bytes or a cell holding U+0000 or a lone surrogate is INVALID_INPUT; either way no table is created.

Input Schema

TableJSON Schema

Name	Required	Description
`why`	No	Required for workspace items: one sentence on what the person is trying to accomplish, in their terms, not a description of this edit. Every workspace write takes one; sessions and summaries record themselves from it. At most 300 characters.
`title`	No	The table's title.
`folder`	No	The folder to file it in: a folder id, or a slug (in workspaceId, else your personal folders).
`schema`	No	The columns instead of headers. Not with headers.
`headers`	No	The first row names the columns. Not with schema.
`audience`	No	Requires workspaceId; defaults internal for internal members, shared for external editors.
`csvContent`	Yes
`description`	No	The table's description.
`workspaceId`	No	Table home (a workspace folder named in folder implies it). A workspace table needs why and takes no visibility. New tables need no expected revision.
`creatorContext`	No	How it was made: the prompt, tool or run.
`inputReferences`	No	What it was made from: ids or URLs.
`parentArtifactId`	No	The artifact this one was derived from.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`table`	Yes
`rowCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already mark this as a non-read-only, non-destructive, open-world write. The description adds substantial behavioral detail beyond that: key uniqueness rules, when INVALID_INPUT or STATE_CONFLICT occurs, and the important atomicity guarantee that no table is created on failure.

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?

The purpose is front-loaded and the paragraph stays tightly focused on CSV import constraints. It is dense and semicolon-heavy, but little of it is irrelevant.

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 a 12-parameter mutation with high schema coverage and an output schema, the description gives enough behavioral context to call it safely, especially around validation and atomic failure. The main remaining gap is that it does not route the agent clearly against sibling table-creation and row-append tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 92%, so the baseline is 3. The description adds meaningful semantics around the headers/schema exclusivity, column-name constraints, unique key behavior, and error-code mapping, though many of those details are also reflected in the schema.

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: creating a table and rows from CSV. This makes the CSV-import intent clear, but it does not explicitly distinguish the tool from the sibling table_create or table_append_rows.

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?

The description gives important usage constraints, notably that headers and an explicit schema are mutually exclusive, and explains validation failures. However, it does not say when to use this tool rather than table_create or table_append_rows, leaving alternative selection implicit.

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

All Tokenrip tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.