Табуля

sheets_list

Read-onlyIdempotent

Lists the sheets of a Tabulya spreadsheet file in tab order: name, position, tab color and frozen rows/columns. Use it to discover sheet names before reading or editing ranges (files_context also returns per-sheet tables and code cells, this one is just the tabs). Read-only. Signature: sheets_list(file_uuid).

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": "sheets_list"
  }
}

Input Schema

Name	Required	Description	Default
`file_uuid`	Yes	UUID of the file.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds tab-order semantics and the per-sheet fields returned, which go beyond the annotations. 'Read-only' restates readOnlyHint=true, so it adds little, but the ordering and field disclosure are genuine value on top of an already well-annotated 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?

Front-loaded with the core action and returned fields, then the routing hint. The trailing 'Read-only. Signature: ...' adds two low-value fragments that duplicate annotations and schema, slightly diluting an otherwise tight description.

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?

An output schema exists, so return values need not be explained, yet the description still names the key fields. For a single-parameter read tool, an agent has everything it needs to choose and call it correctly.

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?

Only one parameter with 100% schema description coverage, so the schema already documents file_uuid. The description's 'Signature: sheets_list(file_uuid)' merely repeats it without adding format or constraint detail, which is the baseline 3 case.

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 and resource (lists the sheets of a file), enumerates the returned fields, and explicitly contrasts itself with files_context. An agent can distinguish it from the sibling before reading any 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 an explicit use case (discover sheet names before reading or editing ranges) and names the alternative with the condition that selects it (files_context returns tables and code cells; this one is just the tabs). Nothing is left to inference.

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?