Skip to main content
Glama

clear_values

Remove data from specified cells in Google Sheets to prepare ranges for new content or reset calculations.

Instructions

Clear values from a range of cells

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_idYesThe ID of the spreadsheet
rangeYesA1 notation range to clear
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool clears values, implying a destructive mutation, but lacks details on permissions needed, whether it's reversible, rate limits, or what happens to formatting (e.g., compared to 'update_cells_format'). This leaves significant behavioral gaps.

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, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand quickly.

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?

Given the tool is a destructive mutation (clearing values) with no annotations and no output schema, the description is incomplete. It does not address critical context like error handling, return values, or side effects, which are essential for safe usage in a spreadsheet environment.

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%, with both parameters ('spreadsheet_id' and 'range') well-documented in the schema. The description adds no additional meaning beyond implying the range is for clearing, which the schema already covers, so it meets the baseline for high schema coverage.

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?

The description clearly states the action ('clear values') and target ('from a range of cells'), which is specific and unambiguous. However, it does not differentiate from sibling tools like 'delete_sheet' or 'find_and_replace', which could also involve removal operations, so it lacks sibling distinction.

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. For example, it does not mention when to choose 'clear_values' over 'delete_sheet' for removing content or 'update_values' for overwriting data, leaving usage context implied at best.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devfinprojects/GAS_MCPSERVER_ADAVANCED'

If you have feedback or need assistance with the MCP directory API, please join our Discord server