Табуля

files_move

Destructive

Moves a rectangular block of cells (values, formats, code) to a new location on the same sheet. source: an A1 rectangle (e.g. 'A1:C10'). target: the top-left cell where the block should land (e.g. 'F1'). References from code/formulas adjust as on the collaboration server. Requires edit permission. Signature: files_move(file_uuid, source, target, 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>",
      "source": "<source>",
      "target": "<target>"
    },
    "name": "files_move"
  }
}

Input Schema

Name	Required	Description
`sheet`	No	Sheet name (defaults to the first sheet).
`source`	Yes	A1 rectangle to move, e.g. 'A1:C10'.
`target`	Yes	Top-left destination cell, e.g. 'F1'.
`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

A3.7/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the edit-permission requirement and that code/formula references adjust as on the collaboration server, which is meaningful behavior for an otherwise destructiveHint=true operation. It stops short of stating what happens to content already occupying the target block, which is a notable omission for a destructive move.

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?

Purpose is front-loaded, followed by compact per-parameter notes and behavioral caveats, all in a tight paragraph. The trailing 'Signature: files_move(file_uuid, source, target, sheet?)' line merely repeats schema data and is the one piece that does not earn its place.

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 an output schema present and annotations covering the safety profile, the description supplies the permission requirement, formula-adjustment behavior, and same-sheet scope — enough for correct invocation. Missing pieces are target-overwrite semantics and the cross-sheet/row-column alternatives, which would round it out.

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 75% and the description's source/target explanations largely restate the schema's own examples, though 'the top-left cell where the block should land' usefully clarifies target semantics. file_uuid is left unexplained in both schema and description; baseline 3 applies when the schema carries most of the load.

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?

Uses a specific verb ('moves') and resource ('a rectangular block of cells (values, formats, code)') with a clear scope ('same sheet'), so the agent knows exactly what content is relocated. It implicitly separates itself from files_move_rows_cols by specifying a block rather than rows/columns, but never names that sibling explicitly.

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

Usage Guidelines3/5

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

The 'same sheet' constraint implies that cross-sheet relocation is out of scope, and the rectangular-block framing hints that whole-row/column movement belongs to files_move_rows_cols, but neither alternative is stated. There is no explicit when-to-use/when-not guidance.

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?