Skip to main content
Glama
Sign In
mcp-gsheets

mcp-gsheets

by freema
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sheets_clear_values

Idempotent

Clears cell contents in a specified range of a Google Sheet using its spreadsheet ID and A1 notation, leaving formatting intact for data reset.

Instructions

Clear values in a specified range of a Google Sheets spreadsheet

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

Input Schema

NameRequiredDescriptionDefault
rangeYesThe A1 notation range to clear (e.g., "Sheet1!A1:B10")
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The description states that the tool clears values, which implies a destructive write operation. The idempotentHint annotation already indicates repeatability, but the description adds no further behavioral context, such as whether formatting or notes are preserved.

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 sentence that immediately states the action and target. It contains no redundant words, making it maximally concise while preserving clarity.

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

Completeness4/5

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

For a simple two-parameter operation with a complete schema and idempotency annotation, the description is sufficient. It could slightly improve by noting that only values are cleared and not formatting, but the core behavior is clear.

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 fully documents both parameters (spreadsheetId and range) with clear descriptions, achieving 100% coverage. The description does not add any additional parameter-specific meaning or examples beyond the schema.

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 the specific verb 'clear' and identifies the resource as 'values in a specified range of a Google Sheets spreadsheet,' which clearly distinguishes it from sibling read, update, and append operations. It is direct and 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?

The description provides no guidance on when to use this tool versus alternatives like sheets_update_values or sheets_append_values. It also does not mention any prerequisites or exclusions, such as the fact that it only affects values and not formatting.

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