Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Append rows to a Google Sheet

append_to_sheet

Append rows of data to an existing Google Sheet by spreadsheet ID, whether it was created in Hermoso or picked from Drive, with an optional range targeting a specific sheet.

Instructions

Append rows to a Google Sheet Hermoso can reach — one it created (pass the spreadsheetId from create_sheet) or one the user handed over with the Google file picker in the app (find its id with list_drive_files). rows = array of row arrays.

Input Schema

NameRequiredDescriptionDefault
rowsYesrows to append — array of row arrays
rangeNorange to append at (default A1 / first sheet)
spreadsheetIdYesthe spreadsheet id from create_sheet

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds useful access constraints and id-discovery paths, but it does not describe append semantics such as where rows land or what happens on repeat calls.

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?

The description is compact and front-loads the core action before adding access and id-source guidance. The sentence is dense but every clause supports correct invocation.

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 simple append mutation, the description covers reachability, spreadsheetId sourcing, and row shape while annotations cover safety and schema covers parameters. It does not explain return behavior, but no output schema exists and this is a minor omission.

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?

Schema coverage is 100%, so all three parameters are already documented. The description reinforces rows as an array of row arrays and clarifies that spreadsheetId can come from create_sheet or list_drive_files, but it omits the optional range parameter.

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 states a specific verb and resource: appending rows to a Google Sheet. It also clarifies reachable-sheet scope, though it does not explicitly distinguish append behavior from update_sheet or other sheet-writing siblings.

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?

It gives clear usage context: the sheet must be one Hermoso created or one the user handed over via the Google file picker, and it names create_sheet and list_drive_files as sources for spreadsheetId. It lacks explicit when-not guidance against update_sheet or clear_sheet_range.

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