Табуля

files_delete

DestructiveIdempotent

Deletes (clears) cells in an A1 range, INCLUDING code cells (Python/Formula), charts and data tables — a touched table is removed entirely. Requires edit permission. Use this to remove or fix content created by files_write/files_run (which cannot overwrite a table). Within the data rows of a server table the range clears their values through the tables service and the table stays; a range covering all of its data rows removes the table, as Delete does in the app. Writes synchronously via collab. Signature: files_delete(file_uuid, range, 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>",
      "range": "<range>"
    },
    "name": "files_delete"
  }
}

Input Schema

Name	Required	Description
`range`	Yes	A1 range to clear, e.g. 'A1' or 'A1:C10'. Any data table intersecting the range is removed entirely.
`sheet`	No	Sheet name (defaults to the first sheet).
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`note`	No
`range`	Yes
`cleared`	Yes
`file_uuid`	Yes
`sequence_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Despite annotations already declaring destructive/idempotent/openWorld, the description adds substantive behavior beyond them: a touched table is removed entirely, edit permission is required, writes are synchronous via collab, and it explains the nuanced table-range semantics (clearing values vs removing the table). This is genuine value-add disclosure.

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 core action and inclusions, then the key use case and table nuance. Dense but nearly every sentence carries decision-relevant information; the signature line is somewhat redundant with the schema but not harmful.

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?

For a destructive tool with an output schema present, the description covers permissions, side effects, table behavior, and synchronicity. Nothing an agent needs to invoke it correctly and safely is missing.

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 67% and already documents the range and sheet parameters with their own descriptions. The description restates the range semantics (table intersection) but provides only a signature line for file_uuid with no added meaning. Baseline 3 is appropriate since the schema does most of the parameter lifting.

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 (deletes/clears) and resource (cells in an A1 range), and explicitly scopes what is included: code cells, charts, and data tables. It is clearly distinguishable from siblings like files_delete_chart, files_delete_rows_cols, and files_table_delete because it names the table-removal behavior uniquely.

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?

Gives a concrete when-to-use: 'remove or fix content created by files_write/files_run (which cannot overwrite a table)'. This routes the agent from write/run to delete when a table is involved. It does not explicitly contrast against the dedicated delete siblings (files_delete_chart, files_table_delete), which keeps it from 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?