Skip to main content
Glama

excel_unmerge_cells

Destructive

Unmerges cells in a specified Excel range, restoring them to individual cells.

Instructions

Unmerge previously merged cells

Input Schema

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

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

The description aligns with the 'destructiveHint: true' annotation, indicating modification. However, it does not detail the exact behavior (e.g., only top-left cell value retained), which would add transparency beyond the annotation. With the annotation already present, the description provides basic context but no extra depth.

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, efficient sentence with no redundancy. It is front-loaded with the core action and resource.

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 description is minimal and does not explain return values (no output schema) or the exact outcome on cell data (e.g., only top-left value kept). Given the tool's simplicity and the presence of destructiveHint, some additional context is missing but not critical.

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 75%, covering 3 of 4 parameters. The tool description does not add any additional meaning beyond what the schema provides for filePath, sheetName, range, and createBackup. Baseline 3 is appropriate given high schema coverage.

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 'Unmerge previously merged cells' clearly states the action (unmerge) and the resource (merged cells), distinguishing it from the sibling 'excel_merge_cells' which does the opposite.

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, such as prerequisites (cells must be merged) or when not to use (e.g., if cells are not merged). No exclusive conditions or alternative tool names 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