Табуля

sheets_color

Sets (or clears) the tab color of a sheet. color: a CSS color string (e.g. '#1F77B4' or 'red'); pass an empty string to clear the color. Requires edit permission. Signature: sheets_color(file_uuid, sheet, color).

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>",
      "sheet": "<sheet>",
      "color": "<color>"
    },
    "name": "sheets_color"
  }
}

Input Schema

Name	Required	Description
`color`	Yes	CSS color (e.g. '#1F77B4'); empty string clears the color.
`sheet`	Yes	Name of the sheet.
`file_uuid`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds useful behavior beyond that: the empty-string clearing semantics and the edit-permission requirement. It does not contradict the annotations; clearing a tab color is not destructive.

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 compact sentences, front-loaded with the action, then the clearing detail, then the permission prerequisite. No sentence is wasted and there is no redundant filler.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description covers the mutation, the clearing case, and the permission requirement. The only minor gap is that file_uuid is left unexplained in both schema and description.

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%, and the description mostly restates the color parameter's format and clear semantics that the schema already documents. It adds the signature with parameter names but says nothing about file_uuid, which is undocumented in both places.

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 opens with a specific verb and resource: 'Sets (or clears) the tab color of a sheet.' It is clearly distinguishable from cell-formatting siblings like files_format and from sheets_rename/sheets_move. An agent can tell what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives implied usage ('pass an empty string to clear the color') and a prerequisite ('Requires edit permission'), but it does not explicitly say when to choose this over alternatives such as files_format for cell colors. There is no when-not-to-use guidance or named sibling routing.

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?