Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by shanebrady77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sheets_read

Retrieve data from Google Sheets by specifying a spreadsheet ID and A1 range, such as 'Sheet1!A1:D10'.

Instructions

Read values from a Google Sheet. Use A1 notation for ranges (e.g. 'Sheet1!A1:D10').

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": "<spreadsheet_id>"
    },
    "name": "sheets_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoSheet1
spreadsheet_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It states the read operation and the A1 notation requirement, which is useful. However, it does not disclose other behavioral aspects such as whether formulas or calculated values are returned, or any potential side effects (though likely none).

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 concise two sentences, front-loaded with the main purpose followed by a usage example. Every word earns its place, with no filler or repetition.

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?

For a simple read tool with an output schema available, the description covers the essential usage: what it does and how to specify the range. It could mention return values, but since output schema exists, that is not necessary. The tool is adequately specified for its simplicity.

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?

Schema description coverage is 0%, but the description compensates by explaining the 'range' parameter with an A1 notation example. The 'spreadsheet_id' parameter is self-explanatory given the tool name and context. This adds meaning beyond the raw schema.

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 the tool's purpose: 'Read values from a Google Sheet.' The verb 'read' and resource 'Google Sheet' are specific, and the A1 notation example further clarifies the action. It is distinguishable from sibling tools like sheets_write or sheets_append.

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 implies usage when you want to read values from a sheet, but it does not explicitly mention alternatives or when not to use it. No exclusions or comparisons to sibling tools are provided, leaving the guidance mostly implicit.

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

Deploy Server

Other Tools