Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_get_info

Read-only

Lists a spreadsheet's tabs with their sizes, title, and URL to help you inspect sheet structure and locate content.

Instructions

List a spreadsheet's tabs with their sizes, plus title and URL.

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

Input Schema

NameRequiredDescriptionDefault
spreadsheetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds that the call returns tab-level metadata rather than cell content, but says nothing about authorization requirements, behavior on an invalid or inaccessible spreadsheetId, or units for 'sizes'.

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?

A single front-loaded sentence with zero filler, and the return payload is stated up front where an agent scanning for it will find it.

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 simple read-only tool with no output schema, the description should fully describe the return shape, and it only sketches it ('tabs with their sizes, plus title and URL') without stating fields like tab IDs or size units. It is adequate to select the tool but leaves ambiguity about exactly what comes back.

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?

With a single required parameter and 0% schema description coverage, the description carries the burden, and 'a spreadsheet's' makes clear that spreadsheetId identifies the target spreadsheet. The name is self-evident, so the lack of explicit ID-format detail is a minor gap for a one-parameter tool.

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 names a specific verb ('List') and resource ('a spreadsheet's tabs') and enumerates the returned fields (tab sizes, title, URL), so an agent can distinguish this metadata call from sheets_read or sheets_analyze. It stops short of explicitly naming a sibling to contrast against.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is only implied: listing tabs with sizes suggests a discovery step before reading or writing tab content, but the agent must infer that from the returned fields.

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