Google Workspace MCP

read_sheet_grid

Extract Google Sheets data including values, formulas, notes, and links from specified ranges for analysis and integration.

Instructions

Read Google Sheets grid data including formatted values, formulas, notes, and links.

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_or_url": "<spreadsheet_id_or_url>"
    },
    "name": "read_sheet_grid"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id_or_url`	Yes
`range_a1`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Mar 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states what data is read without behavioral details like permissions needed, rate limits, error handling, or output format. It mentions data types but lacks operational context.

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 a single, efficient sentence with zero waste, front-loaded with the core action and key details. Every word earns its place without redundancy.

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?

Given complexity (read operation with 2 params, no annotations) and an output schema (which covers return values), the description is minimally adequate but incomplete. It specifies data types read but misses parameter guidance and behavioral context, leaving gaps for effective tool use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain 'spreadsheet_id_or_url' format, 'range_a1' syntax, or default behavior when range is null, leaving parameters undocumented.

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 the verb ('Read') and resource ('Google Sheets grid data') with specific data types included (formatted values, formulas, notes, and links). It distinguishes from sibling 'read_sheet_values' by specifying richer data content, though not explicitly naming alternatives.

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 guidance on when to use this tool versus alternatives like 'read_sheet_values' or 'sheet_to_json' is provided. The description implies usage for reading comprehensive sheet data but lacks explicit context or exclusions.

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

Deploy Server