Skip to main content
Glama

clear_cell_format

Clear cell formatting in a specified range without altering values. Resets styling to default for a clean, consistent look.

Instructions

Clear formatting from cells in range_str without altering cell values.

Args: file_path: Workbook path. sheet_name: Worksheet name. range_str: Range whose formatting should be reset.

Returns: dict: Summary of cleared cells.

Notes: - Non-destructive to cell values but destructive to formatting state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
range_strYes
sheet_nameYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It adds the key behavioral trait: 'Non-destructive to cell values but destructive to formatting state.' It also mentions the return type. It does not discuss permissions or error conditions, so it's not a 5, but it goes beyond a minimal statement.

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 clear sections (Args, Returns, Notes). It is concise, with no redundant text or filler. The main action is front-loaded, and each section serves a purpose.

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?

The tool is relatively simple with three required parameters. The description covers the core action, return value, and a key behavioral note. It lacks details on error handling or file access prerequisites, but it is reasonably complete for its complexity.

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

Parameters4/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. It includes an Args section with one-line definitions for each parameter, adding meaning beyond the names. For example, range_str is described as 'Range whose formatting should be reset.' This is helpful, though not exhaustive.

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 the specific action: 'Clear formatting from cells in `range_str` without altering cell values.' This distinguishes it from sibling tools like clear_range (which likely clears values) and format_cells (which applies formatting), and it specifies the target resource.

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?

The description provides clear context that the tool is for resetting formatting while preserving values, which implies when to use it. However, it does not explicitly mention alternatives or when-not-to-use scenarios, so it falls short of a 5.

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