Google Workspace MCP

read_sheet_values

Extract raw data from Google Sheets by specifying spreadsheet ID and A1 range to retrieve values for analysis or integration.

Instructions

Read raw Google Sheets values for an A1 range.

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_values"
  }
}

Input Schema

Name	Required	Default
`spreadsheet_id_or_url`	Yes
`range_a1`	No
`major_dimension`	No	ROWS
`value_render_option`	No	FORMATTED_VALUE
`date_time_render_option`	No	SERIAL_NUMBER

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Mar 12, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Read raw Google Sheets values'), implying it's non-destructive, but doesn't mention authentication requirements, rate limits, error handling, or what 'raw values' entails. This leaves significant gaps for a tool with 5 parameters.

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 that gets straight to the point with no wasted words. It's appropriately sized for a tool with this complexity and is front-loaded with the core functionality.

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 the tool has 5 parameters with 0% schema coverage and no annotations, the description is incomplete—it doesn't address parameter meanings or behavioral details. However, the presence of an output schema means the description doesn't need to explain return values, preventing a lower score. This is the minimum viable for a read operation with structured output.

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 schema description coverage is 0%, meaning none of the 5 parameters have descriptions in the schema. The tool description adds no information about any parameters beyond implying 'range_a1' relates to 'A1 range'. It doesn't explain what 'spreadsheet_id_or_url', 'major_dimension', 'value_render_option', or 'date_time_render_option' mean or how to use them.

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 action ('Read raw Google Sheets values') and the resource ('for an A1 range'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'read_sheet_grid' or 'search_sheet', which likely have overlapping functionality, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'read_sheet_grid' or 'search_sheet'. It mentions 'raw values' and 'A1 range', but this is part of the purpose statement rather than explicit usage instructions. No context or exclusions are provided.

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

Deploy Server