Табуля

files_list

Read-onlyIdempotent

Lists Tabulya spreadsheet files in a space, most-recently-updated first. Returns each file's uuid, name, createdDate and updatedDate; nextOffset is present when more files remain (pass it back as offset to page). Use this to discover files before reading them with files_read. Signature: files_list(space_uuid?, limit?=100, offset?=0).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "files_list"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size (default 100, max 500).
`offset`	No	Number of files to skip (default 0). Use the `nextOffset` from a previous call to page.
`space_uuid`	No	UUID of the Tabulya space. Optional — auto-detected when you belong to exactly one space; if you belong to several, the error lists them so you can pass one.

Output Schema

Name	Required	Description	Default
`files`	Yes
`nextOffset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description focuses on extra context: result ordering, the returned fields, and how pagination continuation works via nextOffset. Nothing contradicts the annotations; only the absence of hints about large result sets or space-scoping behavior keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose and ordering first, return shape and paging second, workflow guidance third. The signature line slightly restates the schema but earns its place by putting defaults in one glance.

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, yet the description still summarizes returned fields and paging, and the space auto-detection fallback is covered in the schema. Nothing needed to invoke it correctly is missing.

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 100%, so baseline is 3. The description adds value by stating the signature with defaults and explicitly linking nextOffset from a prior call to the offset parameter, which clarifies cross-call parameter flow better than the schema alone.

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 Tabulya spreadsheet files in a space) plus the sort order, which immediately distinguishes it from content-reading siblings like files_read.

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?

Explicitly frames the tool as a discovery step before files_read, giving a clear workflow cue. It doesn't contrast with files_search, which is the other plausible way to find files, so the routing guidance is good but not exhaustive.

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?