Google Sheets and Drive MCP

by Runemal

Overview Schema Source Related Servers Discussions Admin

Python

Remote

freeze_panes

Freeze top rows or left columns in a Google Sheet; use zero values to remove frozen panes.

Instructions

Freeze top rows and left columns; use zero counts to unfreeze.

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

Input Schema

Name	Required	Description	Default
`sheet_name`	Yes
`frozen_rows`	No
`frozen_columns`	No
`spreadsheet_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It covers the core action and the unfreeze mechanism, but omits any safety considerations, permission requirements, or side effects. The behavior is minimally explained.

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 front-loads the purpose and includes a key usage instruction. Every word is necessary and contributes to understanding.

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?

Given the tool's simplicity and the presence of an output schema, the description covers the essential freeze/unfreeze functionality. However, it does not mention required parameters or the sheet-specific context, making it marginally complete for a zero-annotation, zero-schema-coverage scenario.

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 0%, so the description must compensate. It adds meaning to 'frozen_rows' and 'frozen_columns' by linking them to 'top rows and left columns' and explaining zero counts for unfreezing, but does not clarify the required parameters 'spreadsheet_id' and 'sheet_name'.

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 uses a specific verb 'freeze' and resource 'top rows and left columns', clearly distinguishing the tool from siblings like 'clear_range' or 'sort_range'. It also covers the dual purpose of freezing and unfreezing via zero counts.

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 explicitly states when to use zero counts (to unfreeze), providing clear context. It does not elaborate on when not to use the tool or compare with alternatives, but since no sibling tool handles freeze/unfreeze, the guidance is sufficient.

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