Skip to main content
Glama
GhazwaPasha

Google Workspace MCP Server

by GhazwaPasha

sheets_format_cells

Format spreadsheet cells by setting colors, font styles, sizes, and number formats for a specified range in Google Sheets.

Instructions

Format cells — background/text color, bold, italic, font size, number format (e.g. '0.00%', 'yyyy-mm-dd').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boldNo
italicNo
end_colYes
end_rowYes
bg_colorNo
sheet_idYes
font_sizeNo
start_colYes
start_rowYes
text_colorNo
number_formatNo
spreadsheet_idYes

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 disclose behavioral implications. It merely lists formatting options without explaining effects on existing formatting, required permissions, or that the operation modifies a specified range only. This is a significant gap for a mutation tool.

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 a single, concise sentence that front-loads the core function and lists key features without unnecessary detail.

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?

While the description conveys the basic purpose, it omits important context about the required range parameters and potential side effects. However, the output schema and parameter names provide some structure, making the tool usable.

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?

The description adds meaning for formatting parameters by listing them and giving an example for number_format, but it does not explain value formats (e.g., color codes) or the semantics of the range parameters. With 0% schema coverage, this partial compensation is insufficient for full clarity.

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 the tool formats cells and enumerates specific formatting options (colors, bold, italic, font size, number format), distinguishing it from other sheet operations like merging or adding charts. It uses a specific verb ('Format') and resource ('cells').

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 versus alternatives like sheets_batch_update or sheets_update_borders. The description implies usage for cell formatting but does not explicitly exclude other tools or state prerequisites.

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/GhazwaPasha/Google-wrk-spc-mcp'

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