Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__sheets_clear

Destructive

Clear the values in a range, leaving the tab and its formatting in place. This is the non-destructive way to empty a tab or a block of cells — use it instead of deleting and recreating a tab, which throws away the tab's structure along with its 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": "<range>"
    },
    "name": "gws-mcp__sheets_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesRange to clear in A1 notation. A bare tab name clears the whole tab (e.g. "Inventory"), or clear a block with "Inventory!A2:D"
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
spreadsheet_idYesThe spreadsheet ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds the useful detail that formatting and the tab survive while values are removed, and warns that recreating a tab loses structure. However, calling this "the non-destructive way to empty a tab" sits awkwardly against destructiveHint=true and could soften an agent's caution about irrecoverable data loss; it also says nothing about undo/restore or required permissions.

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 sentences, front-loaded with the effect and followed by the alternative it replaces. No filler, no repetition of the tool name, and every clause contributes decision-relevant information.

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 three-parameter, no-output-schema tool with annotations already covering the safety profile, the description covers purpose, effect on surrounding structure, and the safer alternative. The only material gap is what happens to dependent formulas or how to recover cleared data.

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% and the range parameter already documents A1 syntax plus the bare-tab-name shortcut, so the description adds no parameter meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

"Clear the values in a range, leaving the tab and its formatting in place" names a specific verb (clear) and resource (range), and immediately states the boundary condition (structure preserved). This makes it trivially distinguishable from siblings like sheets_delete_tab, sheets_delete, or sheets_update without opening any schema.

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?

It gives an explicit alternative and the condition that selects it: use this "instead of deleting and recreating a tab, which throws away the tab's structure along with its data." That is real routing guidance. It stops short of a 5 because it doesn't name the sibling tool (sheets_delete_tab) or state when clearing is inappropriate (e.g., when formulas elsewhere depend on the cells).

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources