Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create a Google Sheet

create_sheet

Create a new Google Spreadsheet in the user's Drive and optionally fill it with rows, such as exporting a swipefile, ad list, or performance report. Returns the spreadsheet ID and URL.

Instructions

Create a new Google Spreadsheet in the user’s Drive and optionally fill it with rows — e.g. export a swipefile, ad list, or performance report. Pass rows as an array of row arrays (first row = headers). Returns the spreadsheet id + URL. Needs Google Drive connected (Settings > Connectors > Google Drive — one connection covers Drive, Sheets and Docs).

Input Schema

NameRequiredDescriptionDefault
rowsNorows to write — array of row arrays; first row = headers
titleNospreadsheet title

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.9/5.0
Behavior4/5

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

The annotations already declare that this is a non-read-only, non-idempotent, open-world creation tool. The description adds useful context beyond that: it returns the spreadsheet id and URL, rows can optionally be filled, and Google Drive must be connected. It still does not cover failure modes such as duplicate titles or permission errors.

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 front-loaded with the core action, then efficiently covers row formatting, return values, and the connection prerequisite. Every sentence adds practical value with no filler.

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 simple two-parameter creation tool with annotations and no output schema, the description is complete: it explains the output, optional row filling, and the required Google Drive connection. An agent has enough information to invoke the tool correctly.

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 description coverage is 100%, so both parameters are already documented. The description repeats the rows format and header convention without adding meaningful semantics beyond the schema, so the baseline 3 is appropriate.

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: create a new Google Spreadsheet in the user’s Drive. It is clear what the tool does, but it does not explicitly differentiate itself from related siblings such as create_doc, save_to_drive, or append_to_sheet.

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 examples — exporting a swipefile, ad list, or performance report — imply when the tool is useful, and the Google Drive connection prerequisite is stated. However, it does not explicitly say when to use this instead of append_to_sheet, update_sheet, create_doc, or save_to_drive.

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