Skip to main content
Glama
shakhin85

Google Sheets MCP Server

by shakhin85

format_cells

Apply formatting (bold, italic, background color) to a specified range of cells in a Google Sheet.

Instructions

Apply formatting to a range of cells

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boldNoMake text bold
italicNoMake text italic
end_rowYesEnding row index (exclusive)
sheet_idYesThe ID of the sheet
start_rowYesStarting row index (0-based)
end_columnYesEnding column index (exclusive)
start_columnYesStarting column index (0-based)
spreadsheet_idYesThe ID of the spreadsheet
background_colorNoBackground color (RGB values 0-1)
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether formatting overwrites existing formatting, permissions needed, or rate limits. Minimal transparency.

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?

One sentence, very concise. However, it could be slightly more informative without losing conciseness.

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?

Given the complexity (9 parameters, nested object) and lack of output schema or annotations, the description is incomplete. It does not explain return values, permissions, or limitations.

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 100%, so the schema already documents parameters. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Apply formatting to a range of cells' clearly states the verb (apply formatting) and the resource (range of cells). It is specific enough, though it does not differentiate from the sibling tool 'format_cells_advanced'.

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 on when to use this tool versus alternatives like 'format_cells_advanced'. No exclusions or context provided.

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/shakhin85/google-sheets-mcp-server'

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