Mila

update_sheet_tab

Update a spreadsheet (sheet, excel, workbook) tab: merge cells, rename, change color, or resize the grid. Set a cell value to null to clear it.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New tab name
`rows`	No	New row count
`cells`	No	Cells to update in A1 notation (null clears a cell). Each cell is an object with: value (string\|number), and optional format: { bold, italic, underline (booleans), color (text hex e.g. "#FF0000"), bgColor (background hex), fontSize (number), fontFamily (string), align ("left"\|"center"\|"right"), numberFormat ("currency"\|"percentage"\|"number"\|"date"), decimals (number), currencySymbol (string) }. Example: {"A1": {"value": "Revenue", "format": {"bold": true, "bgColor": "#1B3A5C", "color": "#FFFFFF"}}}
`color`	No	Tab color
`tab_id`	Yes	Tab ID
`columns`	No	New column count
`sheet_id`	Yes	Sheet (workbook) ID

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose mutation behavior. It does clarify that null clears a cell, but it fails to explain whether updates are partial or full, whether permissions are needed, or what return value to expect. The misleading 'merge cells' claim is particularly problematic for an agent relying on this text.

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?

The description is short and front-loaded with the action and resource. The second sentence adds a meaningful behavioral note. The phrase '(sheet, excel, workbook)' is slightly cluttered but not harmful.

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

Completeness2/5

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

With 7 parameters, a nested cells object, and no output schema, the description is too terse. It omits update semantics (e.g., whether unspecified fields remain unchanged), required ID dependencies, and any response details. The unsupported 'merge cells' capability further undermines completeness.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds little beyond category-level restatements (rename, color, resize). It incorrectly introduces merge operations not present in the schema, and it does not clarify the nested 'cells' object structure beyond what the schema already provides.

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?

The description clearly identifies the tool as updating a spreadsheet tab and lists operations such as rename, color change, resize, and clearing cells. However, it includes 'merge cells' which is not supported by the schema, and the parenthetical '(sheet, excel, workbook)' adds ambiguity. It does distinguish from sibling tab operations by explicitly mentioning 'tab'.

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?

The description implies usage for modifying an existing tab's properties or content, but it does not explicitly state when to use this tool versus alternatives like create_sheet_tab or update_sheet. There are no exclusions, prerequisites, or references to sibling tools.

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

All Mila tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation5/5

Every tool targets a distinct resource and action: document, sheet, tab, or presentation. Even similar operations like append_rows, append_slides, and append_to_document are clearly differentiated by their intended target.

Naming Consistency4/5

The naming follows a predictable verb_noun pattern with create_, get_, list_, update_, delete_, and append_. Minor deviations like append_to_document (uses 'to') and the use of 'slide_presentation' vs 'slides' keep it from being perfectly uniform.

Tool Count4/5

At 23 tools, the count is slightly above the ideal range, but each tool serves a clear purpose across three resource types (documents, sheets, slides). The volume is justified by supporting tab-level operations and append functionality.

Completeness4/5

The server provides full CRUD plus listing for each resource type, along with tab management and append operations. Minor gaps exist, such as lack of a direct 'set cell value' operation and no slide reorder or delete individual slide, but core workflows are well covered.

Resources

Need Help?