Skip to main content
Glama

set_sheet_color

Change the tab color of a worksheet by providing the sheet index and a hex color value.

Instructions

Set the tab color of a sheet.

Args: sheet: Sheet index (0-based) color: Hex color string (e.g. '#FF0000')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetYes
colorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. However, the description only states 'Set the tab color' without disclosing whether changes are immediate, reversible, or require saving. It also does not mention if color validation occurs or if any side effects exist.

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?

The description is concise with only four lines, using a clear 'Args' section. Every sentence adds value and no unnecessary information is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity and the presence of an output schema, the description is moderately complete. However, it lacks behavioral details (immediacy of effect, reversibility) and does not explain the output. For a straightforward setter, this is acceptable but not fully thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds critical context beyond the input schema: it explains that 'sheet' is a 0-based index and gives an example hex color string ('#FF0000'). Since schema property descriptions are absent (0% coverage), the description fully compensates by clarifying both parameters.

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 clearly states 'Set the tab color of a sheet', combining a specific verb ('Set') and resource ('tab color of a sheet'). Among sibling tools (e.g., add_sheet, rename_sheet, set_cell), this tool's purpose is uniquely distinguishable.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. For example, it does not clarify that this tool changes the sheet tab color rather than cell background colors.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yolonir/ironcalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server