Табуля

files_insert

Destructive

Inserts blank rows or columns into a sheet, shifting existing content down/right. axis: 'rows' or 'columns'. at: the reference line — a column letter (e.g. 'C') for columns, or a row number (e.g. '5') for rows. side: 'before' (default) inserts on the low side (left of the column / above the row), so content at 'at' shifts; 'after' inserts on the high side (right/below). Either way the new line inherits the formatting of the 'at' line. count: how many to insert (default 1). Tables and formulas adjust automatically (recomputed on the collaboration server). Requires edit permission. Signature: files_insert(file_uuid, axis, at, count?, side?, 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>",
      "axis": "<axis>",
      "at": "<at>"
    },
    "name": "files_insert"
  }
}

Input Schema

Name	Required	Description
`at`	Yes	Reference line: column letter ('C') for columns, or row number ('5') for rows.
`axis`	Yes
`side`	No	Insert before (left/above, default) or after (right/below) the 'at' line.
`count`	No	How many to insert (default 1).
`sheet`	No	Sheet name (defaults to the first sheet).
`file_uuid`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructive and non-idempotent annotations, the description explains the mechanics: existing content shifts down/right, the new line inherits formatting from the reference line, tables and formulas adjust automatically via server recomputation, and edit permission is required. This gives the agent substantial operational context needed before invoking a destructive mutation.

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 description is front-loaded with the core action and then systematically explains each parameter and behavioral consequence. It is a bit dense and includes a redundant signature, but it remains efficient for a six-parameter destructive mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description supplies the permissions, formatting inheritance, automatic table/formula behavior, and parameter mechanics an agent needs to call this tool correctly. With an output schema and annotations present, nothing material appears missing.

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

Parameters5/5

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

The description adds meaning beyond the 67%-covered schema: it clarifies the low/high-side semantics of 'side', explains formatting inheritance from the 'at' line, and covers file_uuid and sheet through the signature. It effectively compensates for the schema gaps and makes each parameter's effect concrete.

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?

The description states a specific verb and resource: inserts blank rows or columns into a sheet, with the shifting behavior of existing content. This clearly distinguishes it from sibling mutation tools such as files_delete_rows_cols and files_move_rows_cols.

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?

The description makes clear when the tool is appropriate: inserting blank rows/columns and shifting existing content. It does not explicitly name alternatives or exclusions, but the operation context is unambiguous for an agent choosing among sibling tools.

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?