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.

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": {
      "csvContent": "<csvContent>"
    },
    "name": "table_create_from_csv"
  }
}

Input 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.
`csvContent`	Yes
`description`	No	The table's description.
`workspaceId`	No	Table home: a workspace, by its id or its slug (a workspace folder named in folder implies it). A workspace table needs why and takes no visibility. New tables need no expected revision.
`inputReferences`	No	What it was made from: ids or URLs.
`parentArtifactId`	No	The artifact this one was derived from.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

removedInput schema / properties / audience

Removed value: -{
-  "description": "Requires workspaceId; defaults internal for internal members, shared for external editors.",
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}

removedOutput schema / properties / table / properties / audience

Removed value: -{
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}

Changed1 schema field changedOct 30, 2026

removedInput schema / properties / creatorContext

Removed value: -{
-  "description": "How it was made: the prompt, tool or run.",
-  "maxLength": 16000,
-  "type": "string"
-}

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"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."New value: +"Table home: a workspace, by its id or its slug (a workspace folder named in folder implies it). A workspace table needs why and takes no visibility. New tables need no expected revision."

removedInput schema / properties / workspaceId / format
```
Removed value: -"uuid"
```
addedInput schema / properties / workspaceId / maxLength
```
Added value: +64
```
addedInput schema / properties / workspaceId / minLength
```
Added value: +1
```

removedInput schema / properties / workspaceId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 23, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Beyond the annotations, the description discloses important behavioral details: header trimming, mutually exclusive headers and schema, unique-key enforcement with STATE_CONFLICT, invalid-input conditions, and the crucial guarantee that no table is created on those failures. This adds substantial operational context not covered by the annotations.

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 is dense but purposeful, with no filler. It is somewhat packed with validation rules in long sentences, but every sentence contributes operational information.

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?

The description covers key creation behavior and failure modes well, and the output schema handles return values. However, for a 10-parameter creation tool it does not address when to use this versus the sibling table_create, which is a meaningful completeness gap.

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 90%, so the input schema already documents nearly all parameters. The description reinforces the headers/schema mutual exclusion and adds a few details such as trimmed headers and two blank key cells counting as duplicates, but most parameter meaning is already 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?

The description states a specific verb and resource: create a table and rows from CSV. It is clear what the tool does, but it does not distinguish itself from the sibling table_create, leaving the agent to infer that CSV ingestion is the differentiator.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of table_create or other alternatives. The CSV focus implies the scenario, but the description does not help an agent choose between this tool and general table creation.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.