Skip to main content
Glama
Sign In
Gmail Multi-Inbox MCP Server

Gmail Multi-Inbox MCP Server

by tszaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sheets_get

Retrieve essential Google Sheets metadata including spreadsheet title, available sheet tabs, and row/column counts for each sheet.

Instructions

Get Google Sheets spreadsheet metadata: title, sheet tabs, row/column counts.

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

Input Schema

NameRequiredDescriptionDefault
accountYesAccount id.
spreadsheet_idYesSpreadsheet ID (from the URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the operation is a 'get' (read-only) and specifies the exact return contents (metadata fields). It does not mention potential errors or permissions, but for a simple metadata retrieval, the behavior is sufficiently transparent.

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, concise sentence that is front-loaded with the action and resource, then immediately lists the specific metadata fields. Every word earns its place with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description explicitly lists the return values (title, sheet tabs, row/column counts), which is sufficient for this simple tool. It fully covers the tool's purpose and outputs, with no apparent gaps given the low complexity and minimal parameters.

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?

The input schema already describes both parameters fully (account id and spreadsheet ID from URL), yielding 100% schema coverage. The description does not add additional semantics beyond the schema, so the baseline of 3 is appropriate.

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 verb 'Get' and the resource 'Google Sheets spreadsheet metadata', and explicitly enumerates what that includes: title, sheet tabs, row/column counts. This effectively distinguishes it from sibling tools like sheets_read (which would read cell data) and sheets_create (which creates spreadsheets).

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 when to use the tool (when metadata is needed) but does not explicitly contrast it with alternatives or state when not to use it. There are no exclusions or prerequisite conditions mentioned, though the context is clear enough that it is only 'implied usage' rather than explicit guidance.

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