Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_format

Apply formatting to a Google Sheets range: set bold, italic, text and background colors, number formats, alignment, borders, wrapping, and font size for a selected tab and cell range.

Instructions

Format a range on one tab: bold, colors, number format (e.g. '$#,##0.00', '0.0%', 'yyyy-mm-dd'), alignment, borders.

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": {
      "spreadsheetId": "<spreadsheetId>",
      "tab": "<tab>",
      "startRow": "<startRow>",
      "endRow": "<endRow>",
      "startCol": "<startCol>",
      "endCol": "<endCol>"
    },
    "name": "sheets_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYes
boldNo
wrapNo
endColYes
endRowYesexclusive
italicNo
bordersNo
fontSizeNo
startColYes
startRowYes0-based
textColorNo#RRGGBB
numberFormatNo
spreadsheetIdYes
backgroundColorNo#RRGGBB
horizontalAlignmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the bar is lower, but the description adds no behavior beyond the surface. It does not say whether formatting merges with or replaces existing formatting, whether omitted options are left untouched, or what permission level is needed. The number-format examples are helpful but belong to parameter semantics rather than behavioral disclosure.

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?

A single front-loaded sentence with zero filler: the verb and scope come first, followed by a tight list of format categories with one illustrated example. Every element earns its place and there is no redundant restatement of the tool name.

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 15-parameter mutation tool with no output schema and low schema coverage, the description is thin: it leaves half the options undocumented and says nothing about merge-vs-replace semantics or the response. Cell-range details such as 0-based startRow and exclusive endRow are handled by the schema, but the overall picture remains incomplete for an agent to call this confidently.

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 description coverage is only 27% across 15 parameters, so the description must compensate. It adds real meaning for numberFormat by giving concrete patterns ('$#,##0.00', '0.0%', 'yyyy-mm-dd') and implies textColor/backgroundColor relative to 'colors', but italic, wrap, fontSize and the required range parameters get no mention. Partial compensation justifies a 3 rather than higher.

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 (Format) plus the resource and scope (a range on one tab), then enumerates the kinds of formatting covered (bold, colors, number format, alignment, borders). This cleanly separates it from value-writing siblings like sheets_write or sheets_append_rows. It stops short of naming an explicit alternative, but the purpose is unambiguous.

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?

There is no when-to-use guidance: nothing says to call sheets_write first and then format, no mention of prerequisites such as the range needing to exist, and no exclusions relative to sheets_batch_update. The only implicit context is 'one tab', which is a scope constraint rather than usage guidance.

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