Skip to main content
Glama

sheets_compare_ranges

Read-onlyIdempotent

Compare formatting between two ranges of identical dimensions. Returns a diff of only differing cells and properties, useful for verifying consistent formatting across rows or against a template.

Instructions

Compare cell formatting between two ranges of identical dimensions. Useful for verifying repeated patterns, e.g. "do all data rows 6–85 have identical formatting?" or "is row 10 formatted identically to the template row 5?". Returns a diff listing only the cells and properties that differ between the two ranges. Cells are compared position-by-position; rangeA and rangeB must have the same number of rows and columns. Use fields to restrict comparison to specific format properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoOptional list of format property names to compare, e.g. ["backgroundColor", "textFormat"]. All format properties compared if omitted.
rangeAYesFirst range with sheet prefix, e.g. "Sheet1!A6:Z6"
rangeBYesSecond range with sheet prefix, e.g. "Sheet1!A7:Z7"
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)
useEffectiveFormatNoDefault: false. Compare effectiveFormat (true) or userEnteredFormat (false). effectiveFormat includes conditional formatting overlays.
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses the diff output format, positional comparison semantics, the equal-dimension requirement, and the default behavior when 'fields' is omitted. This provides a clear model of tool behavior.

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 five sentences, each adding substantive information: purpose, examples, output, dimension constraint, and fields guidance. It is front-loaded and contains no fluff or redundant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complete schema and readOnly/idempotent annotations, the description fills remaining gaps: it explains the return format (diff), comparison semantics, and the dimension constraint. The tool's behavior is fully covered for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has 100% description coverage, so the baseline is 3. The description adds value with a concrete example for 'fields' and clarifies that rangeA/rangeB must have matching dimensions, supplementing the schema's field descriptions.

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 opens with a specific verb+resource+scope ('Compare cell formatting between two ranges of identical dimensions') and provides concrete example use cases. It clearly distinguishes this tool from sibling sheet tools by focusing solely on formatting comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage context with examples ('do all data rows 6–85 have identical formatting?') and mentions the 'fields' parameter to restrict comparison. However, it does not explicitly state when not to use the tool or name alternatives, though no sibling tool performs the same function.

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/freema/mcp-gsheets'

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