Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

Get Spreadsheet Values

sheets_get_values
Read-onlyIdempotent

Read cell values from a specified range in a Google Spreadsheet. Returns data as rows or columns in markdown or JSON format.

Instructions

Read cell values from a specific range in a Google Spreadsheet.

Args:

  • spreadsheet_id (string): The ID of the Google Spreadsheet

  • range (string): The A1 notation range to read (e.g., 'Sheet1!A1:D10' or 'A1:D10')

  • major_dimension ('ROWS' | 'COLUMNS'): Return data by rows or columns (default: 'ROWS')

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: { "range": string, "majorDimension": string, "values": [[cell values...], ...] }

Examples:

  • Read range: spreadsheet_id="...", range="Sheet1!A1:D10"

  • Read specific column: spreadsheet_id="...", range="Sheet1!A:A"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_idYesThe ID of the Google Spreadsheet
rangeYesThe A1 notation range to read (e.g., 'Sheet1!A1:D10' or 'A1:D10')
major_dimensionNoWhether to return data by rows or columnsROWS
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds context on response formats (markdown vs JSON) and major_dimension behavior, going beyond annotations without contradiction.

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?

The description is front-loaded with the main purpose. It includes a parameter list and return format, which is slightly redundant with the schema but adds examples. It is well-structured and mostly concise.

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?

With 4 parameters and no output schema, the description covers usage details, examples, and return format. Annotations provide safety context. It is complete enough for an agent to use correctly, though it could mention batch alternatives.

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

Parameters4/5

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

All parameters have schema descriptions (100% coverage). The description adds value with examples, default values, and explanation of response_format outputs, enhancing the schema's meaning.

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 cell values from a specific range in a Google Spreadsheet,' using a specific verb and resource. It distinguishes itself from sibling tools like sheets_append_values and sheets_update_values by focusing on read-only access for a single range.

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 provides examples but does not explicitly state when to use this tool versus alternatives like sheets_batch_get_values for multiple ranges or sheets_get_spreadsheet for entire sheet metadata. Usage context is implied but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EveryInc/google-workspace-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server