Табуля

files_create

Creates a new, empty Tabulya spreadsheet file in a space and returns its uuid. Requires edit permission in the space (or view permission if 'private' is true). Use the returned file_uuid with files_write / files_run / sheets_* to populate it. Signature: files_create(name, space_uuid?, private?).

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": {
      "name": "<name>"
    },
    "name": "files_create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name for the new file.
`private`	No	If true, the file is private to you (default false = shared with the space).
`space_uuid`	No	Space to create the file in. Optional — auto-detected when you belong to exactly one space; if several, the error lists them.

Output Schema

Name	Required	Description	Default
`name`	Yes
`file_uuid`	Yes
`space_uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses permission requirements (edit, or view when private), the returned uuid, and the space auto-detection behavior with its error listing. This is substantial behavioral context that annotations do not cover.

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 purpose and return value in the first sentence, followed by permission and follow-up guidance. The trailing signature line is somewhat redundant with the schema but the description overall remains tight and waste-free.

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?

With an output schema present, the description needn't detail return structure, and it still notes the uuid. Permission model, space auto-detection, and follow-up tools are all covered, so an agent has everything needed to invoke 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?

Schema coverage is 100%, so the schema already documents name, private, and space_uuid including auto-detection. The description adds a conditional permission nuance tied to the 'private' flag, but the explicit signature largely restates schema fields. Baseline 3 is appropriate.

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 ('Creates a new, empty Tabulya spreadsheet file in a space'), plus the return value (uuid). It is clearly distinguishable from siblings like files_write, files_run, and sheets_create.

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 routes the agent to files_write / files_run / sheets_* for populating the new file and states the permission prerequisite. It lacks an explicit 'when not to use' or comparison to sheets_create, but the creation-then-populate flow is unambiguous.

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?