Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

merge_cells

Destructive

Merge a specified range of cells in an Excel worksheet by defining start and end cell coordinates, with optional dry-run preview before applying changes.

Instructions

Merge 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": "merge_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.6/5.0
Behavior2/5

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

Annotations declare destructiveHint=true but the description never explains why: that non-anchor cell contents are discarded on merge, and what dry_run or include_changes would show. For a destructive mutation with low annotation detail (only a hint and a title), the description adds no behavioral context at all.

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

Conciseness3/5

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

One short, front-loaded sentence with zero waste, but the brevity tips into under-specification rather than disciplined concision. Nothing extraneous, yet almost nothing useful either.

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?

A 6-parameter destructive tool with no output schema, 17% schema coverage, and two undocumented optional flags. Given that complexity, a single-sentence description leaves out exactly the details an agent would need before calling it.

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 coverage is 17% – only filepath carries a description, and that one is essentially a path-resolution policy. The description says nothing about the start_cell/end_cell coordinate format, what dry_run previews, or what include_changes controls, so it fails to compensate for the coverage gap.

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?

A specific verb ('merge') plus a specific resource ('a range of cells') makes the basic operation unambiguous. It does not, however, distinguish itself from the closely related siblings unmerge_cells and get_merged_cells, so it stops short of a 5.

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 when-to-use guidance, no prerequisites (e.g. sheet protection or existing merges), and no mention of unmerge_cells as the inverse operation. The agent is left to infer the entire usage context from the name alone.

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