Google Workspace MCP

sheets_get

Read-only

Retrieve the full structure of a spreadsheet, listing each sheet's name, ID, and dimensions. Read this before range queries to ensure you reference the correct sheet name.

Instructions

Spreadsheet structure: every sheet name, id, and dimensions. Read this before a range query so the sheet name is right.

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

Input Schema

Name	Required	Description	Default
`spreadsheetId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful context by specifying that the output is structural metadata (names, ids, dimensions), but it does not describe formatting, ordering, or any edge cases such as empty spreadsheets.

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, focused sentence that front-loads the tool's output and immediately follows with actionable usage guidance. Every word earns its place.

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, safe, one-parameter read-only tool, the description is largely complete: it states what is returned and when to use it. The only notable gap is the lack of explanation around the spreadsheetId parameter, which is mitigated by the schema and the parameter's self-evident name.

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%, and the description does not mention spreadsheetId at all. The parameter name is self-explanatory, but the description provides no additional guidance on where the ID comes from, its format, or why it is required.

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 resource and result: spreadsheet structure including every sheet name, id, and dimensions. It differentiates from sheets_read by indicating this is metadata discovery, not a range query, though it lacks an explicit imperative verb in the first phrase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit guidance: read this before a range query so the sheet name is correct. This implies the right moment to use the tool, though it does not name alternative sibling tools or describe when not to use it.

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