Табуля

files_table_meta

Changes a data table's metadata (without touching its data): rename it, toggle its name bar / column-header row / alternating row colors, or set whether the first data row is the header row. cell: any cell inside the table. Pass only the properties to change. Requires edit permission. Signature: files_table_meta(file_uuid, cell, name?, show_name?, show_columns?, alternating_colors?, first_row_as_header?, 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>",
      "cell": "<cell>"
    },
    "name": "files_table_meta"
  }
}

Input Schema

Name	Required	Description
`cell`	Yes	Any cell inside the table, e.g. its anchor 'A5'.
`name`	No	New table name.
`sheet`	No	Sheet name (defaults to the first sheet).
`file_uuid`	Yes
`show_name`	No	Show the table's name bar.
`show_columns`	No	Show the column-header row.
`alternating_colors`	No	Alternating row colors.
`first_row_as_header`	No	Treat the table's first data row as the column headers.

Output Schema

Name	Required	Description	Default
`cell`	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?

The description adds useful context beyond annotations by emphasizing that the table's data is untouched and that edit permission is required. This is consistent with the annotations declaring a non-read-only, non-destructive mutation, and it helps an agent avoid mistaking this for a data-editing tool.

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 with purpose and property details, and most sentences earn their place. The final 'Signature:' sentence restates schema information and is somewhat redundant, but the overall structure remains efficient.

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?

Given the output schema exists and schema coverage is high, the description is complete enough for an agent to call the tool correctly: it names the operation, the table-targeting method, the editable properties, permission needs, and the metadata-only nature. Minor omissions such as error behavior or boolean defaults are not critical here.

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 already high at 88%, so baseline is 3. The description adds meaningful guidance by listing the changeable properties and explicitly saying to pass only the properties to change, which clarifies optional-parameter usage beyond the schema.

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?

The description states a specific verb and resource: changing a data table's metadata without touching its data, then enumerates the exact metadata properties that can be changed. It clearly distinguishes this from sibling table tools such as files_table_delete, files_table_insert, and files_table_sort.

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?

It gives clear usage context: use it for metadata-only changes, pass only properties to change, and note that edit permission is required. It does not explicitly enumerate when-not-to-use or name a specific alternative sibling, but the metadata-versus-data distinction provides a strong implied boundary.

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?