Skip to main content
Glama
Sign In

Google_sheets

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Sheets Read

sheets_read
Read-onlyIdempotent

Read data from a Google Sheet range. Specify sheet name and range (e.g., 'A1:C10'). Returns rows as arrays of cell values.

Input Schema

NameRequiredDescriptionDefault
rangeYesA1 notation range (e.g., "Sheet1!A1:D10")
spreadsheet_idYesSpreadsheet ID (from the URL)

Output Schema

NameRequiredDescriptionDefault
errorNoError code if connection required
rangeNoA1 notation range of the data read
valuesNoArray of rows, each row is an array of cell values
messageNoError message if connection required
majorDimensionNoRow major dimension (ROWS or COLUMNS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error code if connection required",
+      "type": "string"
+    },
+    "majorDimension": {
+      "description": "Row major dimension (ROWS or COLUMNS)",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection required",
+      "type": "string"
+    },
+    "range": {
+      "description": "A1 notation range of the data read",
+      "type": "string"
+    },
+    "values": {
+      "description": "Array of rows, each row is an array of cell values",
+      "items": {
+        "items": {},
+        "type": "array"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "range": "Sheet1!A1:D10",
+    "spreadsheet_id": "1BxiMVs0XRA5nFMmqvzausWYMYq6nS8twLu0gKBvMZsk"
+  },
+  {
+    "range": "Sales!A1:F100",
+    "spreadsheet_id": "1BxiMVs0XRA5nFMmqvzausWYMYq6nS8twLu0gKBvMZsk"
+  }
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description adds value by specifying the return format ('Returns rows as arrays of cell values'). No contradictions with annotations.

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 two sentences with no extra words. It is front-loaded with the core action and then the return format. Every sentence is necessary.

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?

Given the presence of an output schema and comprehensive annotations, the description is complete enough for this read-only tool. It specifies the range format and return type, which suffices for agent selection.

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 the description adds little beyond the schema. The example of range notation ('A1:C10') is already in schema examples. No additional parameter semantics are provided.

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?

The description clearly states 'Read data from a Google Sheet range,' specifying the verb (read) and resource (Google Sheet range). It provides an example of notation ('A1:C10') which distinguishes it from sibling tools like sheets_write and sheets_append.

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?

The description implies reading data, which is distinct from sibling tools that write or append. It does not explicitly state when not to use or provide alternatives, but the verb 'Read' clearly sets context.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources