Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__sheets_read

Read-only

Read data from a Google Sheets spreadsheet. Returns cell values for one range, or for many ranges in one call: pass range for one block, or ranges for several blocks returned in the order given, each with the range the API echoed back.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "spreadsheet_id": "<spreadsheet_id>"
    },
    "name": "gws-mcp__sheets_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoCell range in A1 notation: "TabName!A1:D10" scoped to a tab the spreadsheet actually has, "A1:Z" for the first tab, or a bare tab name for a whole tab. Give range or ranges, not both.
rangesNoSeveral A1 ranges read in one request, e.g. ["Sheet1!A1:D1", "Sheet1!A2:D50", "Totals!A1:B5"]. The response carries one block per range, in this order, each with rowCount, columnCount and values. Use this instead of several sheets_read calls. Give range or ranges, not both.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
spreadsheet_idYesThe spreadsheet ID (from the URL)
value_render_optionNoHow values are rendered. FORMATTED_VALUE (default) returns what the cell displays. UNFORMATTED_VALUE returns the underlying typed value, which is how you tell a stored number from stored text. FORMULA returns the cell's formula where it has one — the only way to tell a live formula from text that merely looks like one, so use it to verify a write.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description adds useful return behavior. It says many ranges are returned in the order given, each block including the range the API echoed back. It does not cover auth requirements, rate limits, or error behavior, but it adds meaningful context beyond 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, front-loads the purpose, and then explains the single-range versus multi-range return behavior. There is no filler or redundant restatement, and every sentence contributes useful information.

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 read-only tool with five fully described parameters and no output schema, the description covers the essential purpose and return behavior. It explains one-block versus multi-block responses and ordering. It omits some detail about account selection and value rendering, but those are fully covered in the schema.

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 the schema already documents all five parameters in detail. The description reinforces the range-vs-ranges choice and return ordering, but it adds little beyond the schema text. It does not explain value_render_option, account, or spreadsheet_id, which is acceptable given the baseline for full schema coverage.

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: "Read data from a Google Sheets spreadsheet." It also explains that cell values are returned for one range or many ranges in one call. It does not distinguish this tool from sibling readers such as sheets_query, sheets_find_rows, or drive_read_file, so it falls short of a 5.

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 description gives parameter-level usage guidance: use range for one block or ranges for several blocks. However, it does not say when to choose this tool over alternatives like sheets_query, sheets_find_rows, or drive_read_file. There are no explicit exclusions or prerequisites, leaving selection guidance implied.

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

All DataToRAG 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