Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

sheets_values_get

Read-only

Read values from a specified spreadsheet range using A1 notation. Retrieve cell data as rows or columns, formatted or unformatted, or return formulas directly.

Instructions

Read values from a spreadsheet 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": {
      "spreadsheetId": "<spreadsheetId>",
      "range": "<range>"
    },
    "name": "sheets_values_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesA1 notation range (e.g. "Sheet1!A1:D10")
spreadsheetIdYesThe spreadsheet ID
majorDimensionNoROWS or COLUMNS
valueRenderOptionNoFORMATTED_VALUE, UNFORMATTED_VALUE, or FORMULA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

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 safe-read profile is covered. The description adds nothing beyond that: no note on how large ranges or unformatted values behave, no mention of what happens for an empty or nonexistent range, and no side effects to disclose. It effectively restates the annotation.

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 zero waste. It is clean, though the brevity is partly why usage and behavioral detail are absent.

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 4-parameter read-only tool with fully documented schema and clear annotations, the minimum information to call it correctly is present. However, the description leaves out behavioral context an agent would want, such as empty-range handling or the practical effect of valueRenderOption, so it is adequate but with gaps.

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%, including A1 notation guidance for range and the allowed values for valueRenderOption and majorDimension, so the schema carries the semantics. The description contributes no additional meaning beyond that baseline.

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 gives a specific verb and resource: 'Read values from a spreadsheet range,' which cleanly separates it from the write siblings (sheets_values_append, sheets_values_update) and from metadata tools like sheets_get. It stops short of explicitly naming any sibling or scoping the tool against them, so it lands at clear-but-undifferentiated.

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, when-not-to-use, or alternative routing guidance at all. An agent must infer from the name alone whether to reach for sheets_values_get, sheets_get, or sheets_values_append.

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