Табуля

files_read

Read-onlyIdempotent

Reads cell values from a Tabulya spreadsheet file. Pass either 'range' (a single A1-notation range) or 'ranges' (an array of A1 ranges, read in one shot). Returns 2D arrays of display values (strings) from the file's latest live state. If a code cell in a range failed to run, its display value is empty and the failure is reported in a 'code_errors' array ([{cell, error, std_err}]). Signature: files_read(file_uuid, range? | ranges?[], 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_read"
  }
}

Input Schema

Name	Required	Description
`range`	No	A single A1-notation range, e.g. 'A1:C10' (or 'A:A' / '1:1' for whole columns/rows, clamped to data).
`sheet`	No	Sheet name applied to every range (defaults to the first sheet). To mix sheets, omit this and qualify each range, e.g. 'Sheet2!A1:B2'.
`ranges`	No	Multiple A1 ranges (max 20). Each is read independently; a bad range is reported per-range without failing the others.
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`range`	No
`ranges`	No
`values`	No
`file_uuid`	Yes
`code_errors`	No
`sequence_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful context: returned values are display strings from the latest live state, and failed code cells surface in a code_errors array. It does not discuss auth or rate limits, but it meaningfully extends the annotation-covered safety profile.

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 and generally efficient, covering the key invocation and return semantics in a few sentences. The trailing signature partially repeats parameter information already stated, but it remains useful and not bloated.

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 rich annotations, an output schema, and 75% schema coverage, the description supplies enough behavioral context for correct invocation and interpretation. The main omission is explicit sibling routing, but the core read operation is well covered.

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 75%, so the schema documents most parameters, and the description adds the important either/or relationship between range and ranges plus the signature. It also clarifies that sheet applies to every range, which is beyond the schema wording.

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?

The description uses a specific verb and resource: reads cell values from a Tabulya spreadsheet file. It clearly covers the core operation, but it does not explicitly distinguish itself from nearby siblings such as files_read_code or files_get_info.

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 description explains the range vs ranges invocation pattern and notes that values come from the latest live state, which implies when to use it. However, it never states when to choose this over alternatives like files_read_code or files_get_info, nor does it give exclusions.

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?