Табуля

sheets_create

Adds a new (empty) sheet to a Tabulya spreadsheet file. Requires edit permission. If 'name' is omitted, an auto-numbered name is chosen. Optionally insert the sheet before an existing one with 'insert_before'. Applied through the collaboration server. Signature: sheets_create(file_uuid, name?, insert_before?).

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_create"
  }
}

Input Schema

Name	Required	Description
`name`	No	Name for the new sheet (must be unique). Omit for an auto-numbered name.
`file_uuid`	Yes
`insert_before`	No	Name of an existing sheet; the new sheet is inserted before it (defaults to the end).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real context beyond annotations: edit-permission requirement, auto-numbered fallback naming when 'name' is omitted, default append behavior for insert_before, and that the operation is applied through the collaboration server. It doesn't warn that repeated calls are non-idempotent (each call creates a new sheet), which would have earned 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 core purpose and key constraints in tight sentences. The trailing 'Signature: sheets_create(file_uuid, name?, insert_before?)' duplicates information already in the input schema and is 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?

Since an output schema exists, return values needn't be explained. The description covers permissions, naming defaults, and insertion behavior — sufficient for a low-complexity creation tool. Only the non-idempotency implication and file_uuid semantics remain unaddressed.

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 67%, with 'name' and 'insert_before' documented in the schema. The description mostly restates that 'name' can be omitted for an auto-numbered name and that insert_before defaults to the end. The undocumented 'file_uuid' parameter is not clarified beyond the implied spreadsheet target, so the description doesn't fully compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Adds a new (empty) sheet to a Tabulya spreadsheet file.' An agent can tell it creates rather than deletes or renames. It does not distinguish itself from the close sibling sheets_duplicate, so it falls short of a 5.

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 usage context — 'Requires edit permission' and describes the optional insert_before positioning. However, it never states when to prefer this over sheets_duplicate or sheets_list, so no explicit exclusions or alternatives are provided.

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?