Табуля

files_import

Destructive

Imports a CSV, Excel, or Parquet file into a Tabulya spreadsheet. file_name's extension picks the format: .csv (→ a data table at 'cell'), .xlsx/.xls/.xlsm/.xlsb/.ods (→ each workbook sheet becomes a new sheet; 'cell'/'sheet' ignored), .parquet (→ a data table at 'cell'). file_data is the file's bytes, base64-encoded. Requires edit permission. Signature: files_import(file_uuid, file_name, file_data, sheet?, cell?).

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>",
      "file_name": "<file_name>",
      "file_data": "<file_data>"
    },
    "name": "files_import"
  }
}

Input Schema

Name	Required	Description
`cell`	No	Top-left cell for CSV/Parquet (default 'A1'); ignored for Excel.
`sheet`	No	Target sheet for CSV/Parquet (defaults to the first sheet); ignored for Excel.
`file_data`	Yes	The file's raw bytes, base64-encoded.
`file_name`	Yes	File name; its extension determines the format (.csv/.xlsx/.xls/.xlsm/.xlsb/.ods/.parquet).
`file_uuid`	Yes

Output Schema

Name	Required	Description	Default
`summary`	Yes
`file_uuid`	Yes
`sequence_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint, openWorldHint, and non-idempotency, but the description adds material detail beyond them: the edit-permission requirement and the per-format side effects (Excel imports create a new sheet per workbook sheet and ignore cell/sheet). It doesn't note overwrite behavior or size limits, so not a 5.

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 one-line purpose, then format rules, then data encoding and permission. Dense but each sentence carries information; the trailing signature line is largely redundant with the schema and is the only wasted space.

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 what's needed to call it correctly: format dispatch, ignored params, encoding, and permission. Missing only edge-case behavior such as what happens to existing data at the target cell/sheet and the role of file_uuid.

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 80%, but the description adds semantics the schema doesn't: extension-to-behavior mapping, the cell/sheet ignore rule for Excel, and base64 encoding of file_data. file_uuid remains unexplained in both schema and description, which is the one real gap.

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 (imports) and resource (CSV/Excel/Parquet file into a Tabulya spreadsheet), and enumerates the format-specific outcomes per extension. An agent can distinguish this from files_add_table or files_write without opening the 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?

Gives clear operating context: the file extension selects the import behavior, and edit permission is required. It lacks an explicit statement of when to prefer this over sibling tools like files_add_table or files_create, which keeps it 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?