Tokenrip

Create table

table_create

Create a structured table with a typed schema (the title is optional); a column name is 1 to 256 characters with no leading or trailing space, comma or square bracket. At most one column may set unique: true, the table's key. strict rejects unknown columns and invalid values. Use a table for data that grows by adding records: rows are stored once, not copied per change.

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": {
      "schema": "<schema>"
    },
    "name": "table_create"
  }
}

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`	Yes
`strict`	No	Refuse unknown columns and mistyped values on row writes.
`visibility`	No	Standalone sharing only; omit with workspaceId, including private.
`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

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

A3.9/5.0

Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false), the description discloses real behavioral traits: strict mode rejects unknown columns and mistyped values, at most one column can be the unique key, and duplicate key values produce STATE_CONFLICT (via the schema). It does not touch on workspace versus standalone visibility semantics, which is the other non-obvious behavior for this tool.

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?

Front-loaded with the action and its scope, then the decision criterion for using a table at all. It is dense but earns most of its words; the embedded column-name constraints are partly duplicated in the schema, which is the only real waste.

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?

With 10 parameters, a rich input schema at 90% coverage, and an output schema in place, the description covers purpose, usage context, and the two non-obvious write behaviors (strict and the unique key). Only the visibility/workspace interplay is left entirely to the schema, which is a minor 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 description coverage is 90%, so the parameter semantics are already largely carried by the schema. The description's mentions of the optional title, the one-unique-column rule, and strict mode restate what the schema fields already say rather than adding new meaning, so the baseline 3 applies.

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 ('Create a structured table with a typed schema') and bounds the scope with concrete constraints on columns and keys. It does not name or distinguish itself from nearby siblings such as table_create_from_csv, so an agent must infer that difference from the name alone.

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

Usage Guidelines4/5

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

'Use a table for data that grows by adding records: rows are stored once, not copied per change' gives a clear condition for choosing a table over a document-like artifact. It stops short of explicit exclusions or pointing to the CSV-import sibling as the alternative when data already exists in a file.

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.