clear_sheet_data
Clears cell values from a specified range in a Google Sheet using its spreadsheet ID and range reference.
Instructions
シートデータクリア(update_sheet_rangeのエイリアス)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| range | Yes | ||
| spreadsheet_id | Yes |
Clears cell values from a specified range in a Google Sheet using its spreadsheet ID and range reference.
シートデータクリア(update_sheet_rangeのエイリアス)
| Name | Required | Description | Default |
|---|---|---|---|
| range | Yes | ||
| spreadsheet_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the full burden of behavioral transparency. It is silent on whether the operation is destructive, requires specific permissions, or has side effects. The alias reference partially hints at behavior, but insufficiently.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise (one short sentence), but conciseness should not come at the expense of informativeness. It is front-loaded with the alias, which may be useful, but overall the sentence earns its place poorly due to missing critical details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 parameters, no output schema) and sibling tools, the description is incomplete. It does not explain the action's outcome, return value (if any), or prerequisites. The alias reference only partially compensates.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, yet the description adds no information about the parameters. It does not explain the format of 'range' (e.g., A1 notation) or 'spreadsheet_id', leaving the schema as the only reference.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states it clears sheet data and mentions it is an alias of update_sheet_range, providing a verb and resource. However, it lacks specificity about what 'clear' entails (e.g., values only or formatting) and does not differentiate from similar tools like delete_sheet or write_sheet_data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not indicate when to prefer this tool over alternatives, nor does it mention when not to use it. Sibling tools like update_sheet_range, delete_sheet, or clear_sheet_data itself could be confused without context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/overdozer1124/claude-appsscript-pro'
If you have feedback or need assistance with the MCP directory API, please join our Discord server