Skip to main content
Glama

excel_apply_conditional_format

Destructive

Apply conditional formatting rules to an Excel range using conditions, color scales, data bars, or top/bottom rules to highlight key data.

Instructions

Apply conditional formatting to a range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the Excel file
sheetNameYesName of the sheet
rangeYesRange to format (e.g., A1:D10)
ruleTypeYes
conditionNoCondition for cellValue type
styleNoStyle to apply
colorScaleNoColor scale settings
createBackupNo
Behavior2/5

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

The destructiveHint annotation indicates potential modification, but the description adds no behavioral context (e.g., whether it overwrites existing conditional formatting, or any side effects).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no fluff. However, it could be slightly expanded to improve clarity without losing brevity.

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's complexity (8 parameters, nested objects, no output schema), the description is too sparse. It lacks information on rule types, condition structure, or expected behavior after applying formatting.

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

Parameters2/5

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

Schema description coverage is 75% (below 80%), and the tool description does not add any parameter insight beyond the schema. Parameters like 'condition' and 'colorScale' have minimal descriptions that barely clarify usage.

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 action (apply) and resource (conditional formatting to a range). It distinguishes from siblings like excel_format_cell, which deals with direct cell formatting.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., excel_format_cell for direct formatting). No usage context or prerequisites 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/sbraind/excel-mcp-server'

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