Табуля

files_move_rows_cols

Destructive

Reorders whole columns or rows: cuts a column/row range and reinserts it at a destination index, shifting the others and adjusting formula/table references (distinct from files_move, which relocates a rectangular block of cells). axis='columns': range and to are column letters (e.g. range 'B:D', to 'H'); axis='rows': range and to are row numbers (e.g. range '2:5', to '10'). 'to' is the index the range lands before. Requires edit permission. Signature: files_move_rows_cols(file_uuid, axis, range, to, 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>",
      "range": "<range>",
      "to": "<to>"
    },
    "name": "files_move_rows_cols"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Destination column letter (e.g. 'H') or row number (e.g. '10').
`axis`	Yes
`range`	Yes	Columns 'B:D' (or single 'B') / rows '2:5' (or single '3').
`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.4/5.0

Behavior4/5

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

Annotations already declare destructive=true, idempotent=false and openWorld=true, so the safety profile is covered. The description adds real context beyond that: the cut-and-reinsert mechanics, that other rows/columns shift, and that formula and table references are adjusted as a side effect — a non-obvious consequence worth flagging.

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 and front-loaded: the core action and its sibling distinction come first, then axis examples, then the prerequisite. The trailing 'Signature: ...' sentence restates the schema's required parameters and is the one part that doesn't fully earn its place.

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?

An output schema exists, so return values need not be explained. For a 5-parameter mutation tool, the description covers mechanics, side effects, permission requirements, and per-axis argument formats — everything an agent needs to invoke it correctly.

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 60%, and the description compensates by giving per-axis formats for both range and to ('B:D'/'H' vs '2:5'/'10'). Crucially it clarifies that 'to' is the index the range lands *before*, which the schema only calls a 'destination' — that resolves genuine ambiguity. file_uuid and the sheet default are left to the schema.

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 ('Reorders whole columns or rows: cuts a column/row range and reinserts it at a destination index') and explicitly distinguishes itself from the sibling files_move, which relocates a rectangular block of cells. An agent can pick between the two 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 Guidelines4/5

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

Explicitly routes the agent away from files_move and explains the axis-dependent semantics for calling it. It also states the 'Requires edit permission' prerequisite. It lacks an explicit statement of when not to use it (e.g. versus files_insert or files_delete_rows_cols), so it stops just short of a 5.

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?