Skip to main content
Glama

excel_merge_cells

Destructive

Merge cells in a specified range within an Excel sheet. Provide file path, sheet name, and range to consolidate content.

Instructions

Merge cells in a range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the Excel file
sheetNameYesName of the sheet
rangeYesRange to merge (e.g., A1:D1)
createBackupNo
Behavior2/5

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

The annotation destructiveHint already indicates mutation, but the description does not explain what happens during merging (e.g., only top-left cell value remains, potential data loss). With no additional behavioral context, the agent is underinformed.

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 a single 4-word sentence, highly concise and front-loaded. Every word serves a purpose, though more detail could be added at the cost of conciseness.

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

Completeness3/5

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

The tool is simple, but the description omits crucial behavioral details like cell content handling and potential errors. It is minimally adequate for an agent familiar with Excel, but lacks completeness for fully autonomous decision-making.

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%, and the tool description adds no extra meaning to parameters. For example, the 'range' parameter could benefit from syntax examples (e.g., 'A1:D1'). The description fails to enhance understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Merge cells in a range' restates the tool name without adding specificity. It is clear but lacks detail about the outcome (e.g., combining into one cell, preserving top-left content). Among siblings, it distinguishes from 'unmerge_cells' but not from other formatting operations.

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 on when to use this tool versus alternatives like 'excel_format_cell' or 'excel_write_range'. No conditions or prerequisites are mentioned, leaving the agent without context for appropriate invocation.

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