Табуля

files_table_insert

Inserts blank columns or rows INSIDE an existing data table (distinct from files_insert, which inserts sheet-level rows/columns). cell: any cell inside the table. axis='columns' or 'rows'. index: 0-based position within the table to insert at. count: how many to insert (default 1). Server tables (rows on the tables service): rows are inserted only when the table has no sort or filter; new columns always go after its data columns (index is ignored), named by names and typed by kind. Requires edit permission. Signature: files_table_insert(file_uuid, cell, axis, index, count?, names?, kind?, sheet?).

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": {
      "file_uuid": "<file_uuid>",
      "cell": "<cell>",
      "axis": "<axis>",
      "index": "<index>"
    },
    "name": "files_table_insert"
  }
}

Input Schema

Name	Required	Description
`axis`	Yes
`cell`	Yes	Any cell inside the table.
`kind`	No	Server tables, axis='columns': type of the new columns (default text).
`count`	No	How many columns/rows to insert (default 1).
`index`	Yes	0-based index of the data column/row (0 = first data column/row; the table name and header rows are not counted).
`names`	No	Server tables, axis='columns': names of the new columns, one per column (default 'Столбец N').
`sheet`	No	Sheet name (defaults to the first sheet).
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`file_uuid`	Yes
`sequence_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered; the description adds substantial value beyond that with the edit-permission requirement and the server-table rules (rows only inserted when unsorted/unfiltered, columns always appended, index ignored, naming/typing via names/kind). It stops short of saying that inserting shifts existing cells and whether formulas/references survive, which is the one behavior an agent might still need.

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?

Dense but front-loaded: the core distinction comes first, then parameter semantics, then server-table edge cases. The trailing signature line largely duplicates the schema and is the only wasted element.

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?

Given eight parameters, an output schema, and full annotations, the description covers the tricky server-table path and permission requirement that structured fields do not. Only the effect on existing/shifted content and references is left unstated.

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 coverage is 75%, so the schema already does most of the work, but the description adds real meaning on top: it clarifies that index is 0-based within the table, count defaults to 1, and — critically — that index is ignored for server-table columns, which the schema does not say. It also ties names/kind specifically to the server-table column case.

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?

States a specific verb and resource (insert columns/rows inside an existing data table) and immediately scopes it against the sibling files_insert, which handles sheet-level rows/columns. The distinction is explicit enough that an agent can route correctly without opening either schema.

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?

Names the alternative (files_insert) and the condition that selects this tool instead. It also gives the precondition for use (requires edit permission) and the entry point (cell must be inside the table), leaving little to inference.

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

All Табуля 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.

Resources

Need Help?