Skip to main content
Glama

sheets clear range

sheets_clear_range
DestructiveIdempotent

Clears values from a specified A1 range while preserving formatting, so you can remove cell data without deleting rows, columns, or styles.

Instructions

Clear values in an A1 range, keeping formatting. Destructive to cell data.

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_a1": "<range_a1>"
    },
    "name": "sheets_clear_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
range_a1Yes
spreadsheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the description's "Destructive to cell data" is largely redundant. The genuinely additive piece is "keeping formatting," which tells the agent formatting survives while values do not — a real behavioral distinction the annotations do not capture. It does not say what happens to formulas or whether the range must exist.

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?

Two short sentences with zero waste; the core action and the formatting-preservation caveat are both front-loaded. Nothing could be cut without losing information.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Still, for a destructive data operation with 0% parameter documentation, the definition leaves gaps around formula handling, error conditions, and which spreadsheet is targeted.

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 coverage is 0%, so the description must compensate, and it partly does by specifying A1 notation for range_a1. However, spreadsheet_id is given no meaning in the description (relying on the obvious name), and no format examples or multi-range behavior are stated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Clear values in an A1 range" names a specific verb and resource, and "keeping formatting" scopes the operation beyond a generic delete. It separates itself from sheets_update_range by implication (clearing vs. writing), though it never names that sibling.

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?

There is no explicit when-to-use or when-not-to-use guidance. An agent must infer that this is the tool for removing contents while preserving layout, and nothing says whether sheets_update_range with empty values is an alternative or what preconditions (existing range, permissions) apply.

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