Excel MCP Server

Overview Schema Source Related Servers Discussions Admin

format_cells

Apply formatting to Excel cells including fonts, colors, borders, alignment, and number formats to improve data presentation and readability.

Instructions

Apply formatting to Excel cells (fonts, colors, borders, alignment)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filePath": "<filePath>",
      "range": "<range>",
      "styling": "<styling>"
    },
    "name": "format_cells"
  }
}

Input Schema

Name	Required	Description
`filePath`	Yes	Path to the Excel file (.xlsx or .xls)
`range`	Yes	Cell range in A1 notation (e.g., "A1", "A1:C5", "B2:D10")
`styling`	Yes	Formatting options to apply
`sheet`	No	Sheet name (optional, defaults to first sheet)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose that this is a mutation operation (modifies files), potential side effects (overwrites existing formatting), error conditions, or response format. For a tool that modifies Excel files, this is a significant gap in behavioral context.

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?

Extremely concise single sentence with zero waste. Every word earns its place: 'Apply formatting' (action), 'to Excel cells' (target), and parenthetical examples of formatting types. No redundant information or unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after formatting is applied (success/failure indicators), whether changes are saved automatically, or any behavioral constraints. The 100% schema coverage helps with parameters, but overall context for a file-modifying operation is inadequate.

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%, so the schema fully documents all 4 parameters and their nested properties. The description adds minimal value beyond the schema by listing formatting categories (fonts, colors, borders, alignment) which are already detailed in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('Apply formatting') and resource ('to Excel cells'), with specific formatting types listed (fonts, colors, borders, alignment). It distinguishes from siblings like 'write_file' or 'get_cell' by focusing on styling, but doesn't explicitly differentiate from all possible formatting-related tools that might exist.

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 about when to use this tool versus alternatives. There's no mention of prerequisites (e.g., file must exist), when not to use it, or how it relates to sibling tools like 'write_file' (which might also handle formatting). The description assumes the user knows when formatting is needed.

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