Skip to main content
Glama

Google_sheets

by io.github.pipeworx-io

Sheets Create

sheets_create
Idempotent

Create a new Google Spreadsheet. Optionally set title and initial sheet names. Returns spreadsheet ID and sharing URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle for the new spreadsheet

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection required
sheetsNoDefault sheet created with the spreadsheet
messageNoError message if connection required
propertiesNoSpreadsheet properties
spreadsheetIdNoID of the newly created spreadsheet
spreadsheetUrlNoURL to access the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error code if connection required",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection required",
+      "type": "string"
+    },
+    "properties": {
+      "description": "Spreadsheet properties",
+      "properties": {
+        "locale": {
+          "description": "Spreadsheet locale",
+          "type": "string"
+        },
+        "timeZone": {
+          "description": "Spreadsheet timezone",
+          "type": "string"
+        },
+        "title": {
+          "description": "Spreadsheet title",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "sheets": {
+      "description": "Default sheet created with the spreadsheet",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "spreadsheetId": {
+      "description": "ID of the newly created spreadsheet",
+      "type": "string"
+    },
+    "spreadsheetUrl": {
+      "description": "URL to access the spreadsheet",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "title": "Q4 Sales Report"
+  },
+  {
+    "title": "Monthly Budget Tracker"
+  }
+]
  3. First observed

TDQS

C2.3/5.0
Behavior1/5

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

The description claims 'Create a new Google Spreadsheet' implying each call creates a distinct spreadsheet, but annotations set idempotentHint=true, suggesting repeated identical calls have the same effect. This contradiction is not addressed. No disclosure of authorization needs or rate limits.

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

Conciseness3/5

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

The description is a single concise sentence, but it contains inaccuracies (title optional) that undermine its effectiveness. It is short but not clear enough to be reliable.

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

Completeness2/5

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

Given the existence of an output schema, the description adequately notes return values. However, it fails to explain idempotency behavior, error handling, or constraints like duplicate titles, leaving gaps for a tool with complex annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description states that title is optional and mentions 'initial sheet names', but the schema marks title as required and does not include a sheet names parameter. This misleads the agent about required inputs and available options.

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 it creates a new Google Spreadsheet and returns ID and URL, distinguishing it from sibling tools like sheets_read or sheets_write. However, it mentions 'initial sheet names' which is not reflected in the input schema, causing minor confusion.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like sheets_get_spreadsheet or sheets_append. The description does not mention prerequisites or scenarios where other tools would be preferable.

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

All Google_sheets toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Several tools are nearly identical: ask_pipeworx and ask_pipeworx_beta are explicitly the same, and ask_pipeworx, ask_pipeworx_grounded, and deep_research all serve overlapping research/query purposes. discover_tools and suggest_questions both act as discovery entry points, while the five polymarket tools differentiate primarily through intricate details that are easy to confuse.

Naming Consistency2/5

Naming conventions are mixed across the set: verb_noun (ask_pipeworx, resolve_entity, validate_claim), noun_verb (sheets_append, sheets_create), noun_noun (polymarket_arbitrage, entity_profile), and bare verbs (forget, recall, subscribe). The sheets tools are internally consistent but the broader collection has no uniform pattern, with awkward names like pipeworx_trending and search_within.

Tool Count2/5

With 36 tools, the server exceeds the 25-tool threshold for 'too many'. The Google Sheets portion accounts for only 5 tools, while the majority are highly specialized Pipeworx and Polymarket tools that could be consolidated or dramatically reduced. The count feels inflated relative to the advertised 'Google_sheets' server name and its actual core purpose.

Completeness2/5

For a server named Google_sheets, the essential operations exist (create, read, write, append, list structure), but there is no delete/clear range tool and no way to add a new sheet to an existing spreadsheet. For the broader data/research scope, important lifecycles are missing (e.g., no direct way to write Pipeworx results into Sheets, no update for subscriptions, only cancel). The set falls short of fully covering either domain.

Resources