Skip to main content
Glama

Mila

by io.github.mila-gg

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
NameRequiredDescriptionDefault
nameNoNew tab name
rowsNoNew row count
cellsNoCells 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"}}}
colorNoTab color
tab_idYesTab ID
columnsNoNew column count
sheet_idYesSheet (workbook) ID

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

The description provides one behavioral hint: setting a cell value to null clears it. However, it lacks disclosure of side effects, partial update behavior, or what happens when resizing the grid, which is especially important given no annotations are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two-sentence structure is efficient, but the first sentence is awkward with redundant parenthetical and the unverified 'merge cells' claim. It could be streamlined to focus on actual parameters.

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?

For a tool with 7 parameters, nested objects, and no annotations or output schema, this description is incomplete. It doesn't cover error behavior, partial updates, or the full scope of formatting options, leaving the agent to rely solely on the schema.

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 baseline is 3, but the description adds nothing beyond the schema—it even mentions 'merge cells' which has no corresponding parameter. The null-clearing behavior is already documented in the schema's cells description.

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 states it updates a spreadsheet tab with actions like rename, change color, and resize. However, the mention of 'merge cells' is not reflected in the schema, creating ambiguity about the tool's actual capabilities.

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?

No guidance is provided on when to use this tool instead of 'update_sheet' or other siblings. The description only states the general update purpose without defining exclusions or alternative scenarios.

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

All Mila toolsInspect
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.6/5.0
Disambiguation5/5

Each tool maps to a distinct resource and action: documents, sheets, slides, and servers. Even similar operations like update_sheet and update_sheet_tab are clearly separated by scope (workbook vs tab).

Naming Consistency4/5

Most tools follow a verb_noun pattern (create_document, delete_sheet_tab, list_slides), but there are minor deviations: 'append_to_document' vs 'append_rows'/'append_slides', and 'create_slide_presentation' vs 'list_slides' use inconsistent naming lengths and pluralization.

Tool Count4/5

With 23 tools, the server is slightly above the ideal 3–15 range but reasonable for covering three full document-type lifecycles (documents, spreadsheets, presentations) plus server listing. No tool feels redundant.

Completeness4/5

The server provides create, read, update, delete, list, and append operations for documents, sheets, and presentations, including tab-level management for spreadsheets. Minor gaps exist like no individual slide update or search across all resource types, but the core workflows are well-covered.

Resources