Skip to main content
Glama
Longtran2404

mcp-google-sheets-server

by Longtran2404

sheets_conditional_formatting

Apply conditional formatting rules to a specified cell range in a Google Sheet, setting text or background colors based on comparison rules.

Instructions

Apply conditional formatting rules to cells

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYesThe range to apply conditional formatting
valueNoValue to compare against
ruleTypeYesType of conditional formatting rule
textColorNoText color when condition is met
spreadsheetIdYesThe ID of the spreadsheet
backgroundColorNoBackground color when condition is met

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.2/5.0
Behavior2/5

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

There are no annotations and the description only says 'apply', revealing minimal behavioral detail. It does not disclose whether existing conditional formatting rules are replaced, merged, or how invalid ranges or rule conflicts are handled.

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, direct sentence with no filler or redundant wording. It is appropriately sized and front-loaded with the core action.

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?

The description is too thin for a tool with six parameters, nested color objects, and no output schema. It lacks examples, rule-type behavior, effect on existing formatting, and color object structure, leaving significant gaps for correct invocation.

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?

All top-level parameters have one-line descriptions, giving 100% schema coverage, but the descriptions are minimal. The nested textColor and backgroundColor objects have no property definitions, and value's dependence on ruleType is not explained.

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 operation ('apply conditional formatting rules') and the target ('cells'). 'Conditional formatting' distinguishes this from sibling tools like sheets_format_cells or sheets_set_data_validation.

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 given on when to use this tool versus siblings such as sheets_format_cells or sheets_set_data_validation. There is also no mention of when not to use it or any alternative approaches.

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