Табуля

files_rerun

Re-runs existing code cells (Python/SQL) WITHOUT changing their code — e.g. to refresh external data. range: an A1 selection of code cells to re-run; omit it to re-run every code cell on the sheet. Execution is ASYNCHRONOUS: returns a task id immediately; read results with files_read after a few seconds. (To set new code, use files_run; this only re-runs unchanged code.) Requires edit permission. Signature: files_rerun(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>"
    },
    "name": "files_rerun"
  }
}

Input Schema

Name	Required	Description
`range`	No	A1 selection of code cells to re-run; omit to re-run all code cells on the sheet.
`sheet`	No	Sheet name (defaults to the first sheet).
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`note`	Yes
`status`	Yes
`task_id`	Yes
`file_uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing asynchronous execution, that a task id is returned immediately, and that results must be read with files_read after a few seconds — behavior no annotation conveys. It also states the edit-permission requirement, consistent with readOnlyHint=false and idempotentHint=false.

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 and dense — scope, async behavior, permission, and sibling disambiguation arrive in that order with no filler. Minor redundancy between 'WITHOUT changing their code' and 'this only re-runs unchanged code' costs a point.

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 an async mutation tool with three parameters, it covers everything an agent needs: what happens, what's returned, how to get results, what permission is required, and how to avoid the wrong sibling. The output schema exists, yet the description still usefully explains the task-id/read-back loop.

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 the description's range/sheet explanations largely restate what the schema already says. The one gap, file_uuid having no description anywhere, is not filled; the 'Signature:' line adds call shape but not semantic meaning. Baseline 3 is appropriate where the schema does most of the work.

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+resource ('Re-runs existing code cells (Python/SQL)') plus the defining constraint ('WITHOUT changing their code') and the motivating use case ('refresh external data'). It explicitly contrasts with the sibling files_run, so an agent can select 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?

Gives explicit when-to-use ('refresh external data'), when-not ('To set new code, use files_run; this only re-runs unchanged code'), and the omitted-parameter behavior ('omit it to re-run every code cell on the sheet'). Alternatives and conditions are both named.

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?