Skip to main content
Glama

Format Sheet Range

format_sheet_range

Apply formatting to a Google Sheets range: colors, number formats, text wrapping, alignment, and font styling. Use hex codes for colors (e.g., #FFEECC) and specify format types like DATE or CURRENCY.

Instructions

Applies formatting to a range: colors, number formats, text wrapping, alignment, and text styling.

Colors accept hex strings (#RRGGBB). Number formats follow Sheets types (e.g., NUMBER, CURRENCY, DATE, PERCENT). If no sheet name is provided, the first sheet is used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
spreadsheet_idYesThe ID of the spreadsheet. Required.
range_nameYesA1-style range (optionally with sheet name). Required.
background_colorNoHex background color (e.g., "#FFEECC").
text_colorNoHex text color (e.g., "#000000").
number_format_typeNoSheets number format type (e.g., "DATE").
number_format_patternNoCustom pattern for the number format.
wrap_strategyNoText wrap strategy - WRAP (wrap text within cell), CLIP (clip text at cell boundary), or OVERFLOW_CELL (allow text to overflow into adjacent empty cells).
horizontal_alignmentNoHorizontal text alignment - LEFT, CENTER, or RIGHT.
vertical_alignmentNoVertical text alignment - TOP, MIDDLE, or BOTTOM.
boldNoWhether to apply bold formatting.
italicNoWhether to apply italic formatting.
font_sizeNoFont size in points.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description adds useful behavioral details beyond annotations: color format constraints, number format types, and default sheet behavior. Annotations already indicate safe modification (destructiveHint=false), so the description complements them well.

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 extremely concise: two sentences that front-load the main purpose and include key details. Every sentence earns its place, with no fluff.

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

Completeness4/5

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

Given the tool's complexity (13 parameters), full schema coverage, output schema presence, and annotations, the description is largely complete. It could mention that formatting applies only to specified properties, but overall adequate.

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?

With 100% schema description coverage, baseline is 3. The description adds value by explaining color format (hex strings), number format types (Sheets types), and default sheet behavior, improving understanding beyond the schema.

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 clearly states the tool applies formatting to a range, listing specific formatting types (colors, number formats, etc.). It is specific with verb 'applies' and resource 'range', but does not explicitly differentiate from siblings like 'manage_conditional_formatting', so not a 5.

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

Usage Guidelines3/5

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

The description provides a tip about default sheet behavior but offers no guidance on when to use this tool versus alternatives (e.g., conditional formatting). Usage context is implied but not explicit.

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/chadvdwww-hash/worksuite-mcp'

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