Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Write to a range in a Google Sheet

update_sheet
DestructiveIdempotent

Correct values in a Google Sheet by writing to an exact range; existing data is protected until you confirm overwriting, so wrong cells can be fixed in place.

Instructions

CORRECT cells in a Google Sheet — write values to an exact range, overwriting whatever is there. This is the fix append_to_sheet cannot make: appending only ever adds rows at the bottom, so without this a wrong number stays wrong forever and the only "correction" is a second row contradicting the first. Pass range (e.g. "B2:C5", or "Q3 Report!B2" to name a tab — list_sheet_tabs gives the names) and values as an array of row arrays; an anchor cell like "B2" is fine and the block is written down and right from it. Writing into EMPTY cells goes straight through. Writing OVER cells that already hold values is REFUSED first, naming exactly how many filled cells would be overwritten — show the user that, get a yes, then call again with confirm:true. The result is READ BACK from the sheet, so what you report is what the sheet now holds rather than what Google accepted.

Input Schema

NameRequiredDescriptionDefault
rangeNoA1 range or anchor cell, e.g. "B2:C5", "B2", or "Q3 Report!B2" (default A1)
valuesNoarray of row arrays to write
confirmNorequired only when the target range already holds values
updatesNowrite SEVERAL disjoint ranges in one call, instead of range+values
sheetUrlNo
spreadsheetIdNo
valueInputOptionNoUSER_ENTERED (default) parses formulas, dates and numbers the way typing them would; RAW stores every value as literal text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.454
    • removedInput schema / properties / updates / items / properties / values / items / items / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / updates / items / properties / values / items / items / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
    • removedInput schema / properties / values / items / items / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / values / items / items / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  2. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the crucial safety behavior beyond that — writes over filled cells are refused first and report how many cells would be lost, requiring an explicit confirm:true retry. It also discloses that the returned result is read back from the sheet rather than echoing what the API accepted, which is exactly the kind of context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action ("CORRECT cells ... write values to an exact range"), then layers on the append comparison, parameter formats, the confirm flow, and the read-back guarantee in roughly priority order. It is longer than most definitions because each paragraph carries distinct operational information, though the emphasized capitalization and the extended append_to_sheet framing add some bulk that could be trimmed.

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?

For a destructive mutation tool with no output schema, the description covers the safety gate, the confirmation loop, input formats for the two primary parameters, and the provenance of the returned values. Combined with annotations that declare destructiveness and idempotency, an agent has everything needed to call this correctly and to avoid silent data loss.

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 71%, and the description adds real meaning beyond it: range accepts an A1 range, an anchor cell, or a tab-qualified reference, values are arrays of row arrays, and an anchor cell writes the block down and right from it. It also documents confirm's purpose in the overwrite flow. It does not touch updates, sheetUrl, spreadsheetId, or valueInputOption, so it stops short of full coverage of the 7 parameters.

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 ("write values to an exact range") and immediately distinguishes itself from the closest sibling, append_to_sheet, by explaining that appending cannot correct existing values. An agent can tell exactly what this tool does and why it differs from the alternatives without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative (append_to_sheet) and the condition that selects this tool over it, then spells out the full two-step flow: an overwrite attempt is refused with a count of filled cells, the user must confirm, and the call is repeated with confirm:true. Writing into empty cells is stated to pass straight through, so both branches of the decision are covered.

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