Google Sheets and Drive MCP

by Runemal

Overview Schema Source Related Servers Discussions Admin

Python

Remote

sort_range

Sort a bounded range in a Google Sheet by named columns, with optional sort order and header row preservation.

Instructions

Sort a bounded range by named columns while preserving header rows.

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>",
      "range": "<range>",
      "sort_columns": "<sort_columns>"
    },
    "name": "sort_range"
  }
}

Input Schema

Name	Required	Default
`range`	Yes
`sort_order`	No	ASCENDING
`header_rows`	No
`sort_columns`	Yes
`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

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full behavioral disclosure burden. It only mentions 'preserving header rows', but omits critical details like that sorting modifies the range in-place, requires edit permissions, or how ties are handled. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, but it sacrifices necessary detail for brevity. While front-loaded with the core action, it lacks the completeness expected for a tool with five parameters.

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

Completeness2/5

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

Despite having an output schema, the description fails to provide essential context for a mutable operation: it does not state that the sort is applied in-place, that header rows are preserved but not sorted, or any side effects. The minimal information leaves significant gaps for correct invocation.

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 tool description does not explain any parameters beyond implying 'named columns' corresponds to sort_columns. Key parameters like range syntax, sort_order effect, and header_rows interpretation are undocumented, leaving the agent to infer from names alone.

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 'Sort a bounded range by named columns while preserving header rows' clearly states the action (sort), the resource (bounded range), and key constraints (by named columns, preserving headers). It distinguishes this tool from siblings like read_range or write_range, making its purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as when sorting is preferable to filtering or other data manipulation. There are no conditions, prerequisites, or exclusion criteria mentioned.

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