Skip to main content
Glama

clear_range

Destructive

Clears the contents of a rectangular cell range in an Excel worksheet. Specify the start and end cells to remove values from that block.

Instructions

Clear values from a rectangular range of cells.

Args: file_path: Path to workbook. sheet_name: Worksheet name. start_cell: Top-left cell of range to clear. end_cell: Bottom-right cell of range to clear.

Returns: str: Success message.

Raises: (Propagates exceptions from the underlying tools on I/O or invalid ranges.)

Notes: - Destructive: clears cell values (but not necessarily styles) — mention in API docs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_cellYes
file_pathYes
sheet_nameYes
start_cellYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description adds useful behavioral context beyond the destructiveHint annotation: it specifies that cell values are cleared but styles may not be, and it discloses exception propagation behavior. This enriches the annotation rather than contradicting it.

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 well-structured with Args, Returns, Raises, and Notes sections. It is concise with no filler, and each line serves a purpose.

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

Completeness5/5

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

The description covers all required parameters, return type, error behavior, and destructive nature. Even with an output schema present, it provides necessary context for a destructive operation, making it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing one-line explanations for all four parameters (file_path, sheet_name, start_cell, end_cell) that clarify their roles beyond what the schema gives.

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 clearly states 'Clear values from a rectangular range of cells' with a specific verb and resource, and it is distinct from siblings like clear_cell_format (which clears formatting).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but provides no explicit guidance on when to use it versus alternatives like clear_cell_format or write_cells. The destructive note implies caution, but no alternative tools are mentioned.

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/mbeps/excel-mcp'

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