Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_read

Read-only

Read cell values from a Google Sheets range using A1 notation, such as 'Sheet1!A1:D50' or a whole tab name. Returns formatted, unformatted, or formula values for analysis.

Instructions

Read values from a range in A1 notation, e.g. 'Sheet1!A1:D50' or just 'Sheet1' for the whole tab.

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": {
      "spreadsheetId": "<spreadsheetId>",
      "range": "<range>"
    },
    "name": "sheets_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
valueRenderNoFORMATTED_VALUE
spreadsheetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description discloses nothing behavioral: no mention of how values are returned, size limits, empty-range behavior, or what valueRender actually changes. Only the range syntax is added, which is parameter semantics rather than behavior.

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?

A single front-loaded sentence with a concrete example that earns its place by resolving the range-format ambiguity. Nothing is padded, though the space saved could have been spent on the undocumented enum parameter.

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

Completeness3/5

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

For a simple three-parameter read tool with no output schema, the definition is minimally viable: an agent knows what to call and how to format the range. It leaves gaps on the return shape (values array vs. formatted grid) and on valueRender's effect, which matter because no output schema exists to fill them in.

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 0%, so the description carries real weight, and it does clarify the most error-prone parameter: range accepts A1 notation like 'Sheet1!A1:D50' or a bare tab name for the whole sheet. However, spreadsheetId and especially valueRender (the one enum, with a default) get no explanation of what each mode yields.

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 opens with a specific verb and resource: 'Read values from a range' in a spreadsheet context, and the A1 example makes the target object unambiguous. It implicitly contrasts with the write/append siblings via 'Read', but never names an alternative, so it stops 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no routing to alternatives such as sheets_get_info or sheets_analyze. The agent must infer from the name alone that this is the tool for pulling cell data versus tab metadata or aggregated analysis.

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