Skip to main content
Glama
Sign In
mcp-gsheets

mcp-gsheets

by freema
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sheets_get_merged_cells

Read-onlyIdempotent

Get all merged cell ranges for a sheet, returned in A1 notation and GridRange coordinates.

Instructions

Get all merged cell ranges for a specific sheet. Returns each merge as A1 notation and GridRange coordinates.

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

Input Schema

NameRequiredDescriptionDefault
sheetNameYesName of the sheet (tab) to inspect
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds the return format (A1 notation and GridRange coordinates), which is useful beyond the annotations. It does not discuss errors or empty results, but the safety profile is well covered.

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?

One concise, front-loaded sentence that states the operation and result format. Every word earns its place, with no fluff or redundancy.

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?

Given the low complexity, high schema coverage, and read-only annotations, the description fully covers the tool's purpose, scope, and return format. No output schema exists, but the return format disclosure is sufficient for this simple getter.

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% for both parameters (spreadsheetId and sheetName), with clear descriptions. The tool description does not add extra parameter-specific meaning, but the schema already provides sufficient semantics, 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 'merged cell ranges' with scope 'for a specific sheet'. It unambiguously distinguishes from sibling tools like sheets_merge_cells (action) and sheets_unmerge_cells.

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 implies the use case: to retrieve all merged ranges from a sheet. It does not explicitly mention alternatives or exclusions, but the purpose is clear enough that an agent can infer when to use it. The readOnlyHint annotation reinforces it as a safe inspection tool.

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