Skip to main content
Glama
Hermoso

Hermoso

Official

Format a Google Sheet

format_sheet
DestructiveIdempotent

Make exported sheets readable by bolding headers, freezing top rows, and auto-sizing columns so content is not cut off.

Instructions

Make an exported sheet readable: bold the header row, FREEZE it so it stays visible while scrolling, and auto-size the columns so nothing is cut off. Worth calling right after create_sheet — a raw export with unsized columns and a header that scrolls away is the difference between a spreadsheet someone reads and one they close. Changes no cell VALUE, so it is never gated. The defaults do all three on the first tab; pass tab to pick another, freezeRows:0 to skip freezing, boldHeader:false or autoResize:false to skip those.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "format_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNotab title or numeric sheetId (default: the first tab)
sheetUrlNoGoogle Sheets link, instead of spreadsheetId
autoResizeNoauto-size columns to fit their content; default true, false skips it
boldHeaderNobold the header row; default true, false skips it
freezeRowsNohow many top rows to freeze (default 1, 0 = none)
spreadsheetIdNoGoogle spreadsheet id; use this or sheetUrl

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.465
    • addedInput schema / properties / autoResize / description
      Added value: +"auto-size columns to fit their content; default true, false skips it"
    • addedInput schema / properties / boldHeader / description
      Added value: +"bold the header row; default true, false skips it"
    • addedInput schema / properties / sheetUrl / description
      Added value: +"Google Sheets link, instead of spreadsheetId"
    • addedInput schema / properties / spreadsheetId / description
      Added value: +"Google spreadsheet id; use this or sheetUrl"
  2. Addedv0.1.161

TDQS

A4.4/5.0
Behavior4/5

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

Adds context beyond the annotations: it discloses that no cell VALUE is modified, only presentation, which scopes the meaning of destructiveHint=true (existing formatting may be overwritten, but data is safe). It also asserts the call 'is never gated', a useful operational fact not encoded in annotations. It could go further by stating explicitly that pre-existing formatting on the target tab is replaced.

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?

Front-loaded with the three actions, then the usage rationale, then the parameter opt-outs — a natural decision order. Every sentence carries information; nothing is filler despite the length.

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?

For a 6-parameter mutation tool with no output schema, it covers what changes, what does not change, defaults, and when to call it. It leaves unstated whether existing formatting on the tab is overwritten and what the call returns or costs, which is the remaining gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value by explaining the default behavior ('the defaults do all three on the first tab') and the exact opt-out idioms for tab, freezeRows, boldHeader, and autoResize. It ties parameters to user-visible outcomes rather than just restating types.

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?

States a specific verb and resource ('make an exported sheet readable') and enumerates the three concrete operations performed: bold header, freeze header, auto-size columns. This clearly separates it from siblings like update_sheet (which edits values), read_sheet, and create_sheet.

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?

Gives explicit timing and rationale — 'Worth calling right after create_sheet' — plus per-flag opt-outs (freezeRows:0, boldHeader:false, autoResize:false) so an agent knows how to narrow the behavior. It stops short of naming a competing tool to use instead, but no sibling overlaps in function, so the gap is minor.

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

Deploy Server

Other Tools