Skip to main content
Glama
SheetForge MCP

SheetForge MCP

by iHeldan

insert_columns

Destructive

Insert one or more columns beginning at a chosen column in an Excel worksheet to add or reorganize sheet data.

Instructions

Insert one or more columns starting at the specified column.

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_col": "<start_col>"
    },
    "name": "insert_columns"
  }
}

Input Schema

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

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 only flag destructiveHint=true; the description adds nothing about the key behavioral consequence that existing cells shift right and referencing formulas may change. It also never mentions the available dry_run safeguard or default count of 1, both of which materially affect how an agent should call a destructive mutation.

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?

A single front-loaded sentence with zero waste, but for a 5-parameter destructive tool it is under-specified rather than tight. Brevity here costs correctness.

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?

With no output schema, sparse schema docs, and only a destructiveHint annotation, the description should carry far more: sheet targeting, shift semantics, dry_run usage, and indexing conventions. It leaves all of that to guesswork.

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 20% (only filepath is documented), so the description must compensate and does not: start_col's indexing base (0- vs 1-based), count's default of 1, and dry_run's purpose are all left 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?

States a specific verb+resource ('Insert ... columns') and its insertion point ('starting at the specified column'), which clearly separates it from sibling delete_sheet_columns and insert_rows. It omits the worksheet/file scope, but the resource is unmistakable.

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 versus insert_rows, delete_sheet_columns, or write_data_to_excel, and no mention of prerequisites such as sheet protection or whether formulas in shifted columns are adjusted. The agent must infer all routing.

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