Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

unmerge_cells

Destructive

Unmerge cells in a specified worksheet range to restore individual cells for editing or formatting.

Instructions

Unmerge a range of cells.

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>",
      "sheet_name": "<sheet_name>",
      "start_cell": "<start_cell>",
      "end_cell": "<end_cell>"
    },
    "name": "unmerge_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
end_cellYes
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
sheet_nameYes
start_cellYes
include_changesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • addedInput schema / properties / filepath / description
      Added value: +"Reuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing."
  2. First observedv0.8.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, so the safety profile is known, but the description adds nothing beyond that: it does not say what happens to the underlying values or formatting (only the top-left cell's content is typically kept), nor does it explain the dry_run or include_changes options that mitigate that risk.

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?

A single short sentence with no filler and the action front-loaded. Its brevity is more under-specification than verbosity, which is penalized elsewhere, so structure itself is fine.

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 destructive mutation with 6 parameters, 17% schema coverage and no output schema, the description should at least cover the dry_run escape hatch and data-loss semantics. It leaves an agent without enough to call this safely or correctly.

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 only 17% — only filepath is documented, and even that lives in the schema, not the description. The description's phrase 'a range of cells' weakly implies start_cell/end_cell but says nothing about sheet_name, dry_run, or include_changes, leaving most of the 6 parameters unexplained.

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 states a specific verb and resource ('Unmerge a range of cells'), which is unambiguous. However, it does not differentiate from the close siblings merge_cells and get_merged_cells, so the agent gets no routing signal from the text itself.

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?

There is no guidance on when to use this versus merge_cells or when to inspect existing merges with get_merged_cells first. It also gives no precondition such as the range actually containing merged cells.

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

Deploy Server

Other Tools