Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_sheet_rows

Destructive

Delete one or more rows from a specified Excel sheet starting at a chosen row, with optional count and dry-run preview for safer workbook edits.

Instructions

Delete one or more rows starting at the specified row.

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_row": "<start_row>"
    },
    "name": "delete_sheet_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
dry_runNo
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
start_rowYes
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.9/5.0
Behavior3/5

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

The annotations already disclose destructiveHint=true, so the destructive nature is covered. The description adds useful scope by saying it deletes one or more rows starting at start_row, but it does not explain irreversibility, whether dry_run previews changes, or any permission requirements.

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?

The description is a single front-loaded sentence with no wasted words. However, for a destructive five-parameter tool, that brevity leaves significant omissions, so it is concise but arguably too sparse.

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 and a destructive operation, the description should clarify dry_run behavior, required filepath/sheet_name context, and consequences of deletion. It leaves those gaps despite annotations only covering destructiveness.

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%, and the description compensates only partially by implying that count and start_row define a contiguous row deletion. It does not clarify dry_run, sheet_name, or how filepath should be supplied beyond the schema's filepath note.

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: delete rows, with scope 'starting at the specified row' and 'one or more rows.' It distinguishes itself from delete_sheet_columns by operating on rows, but it does not explicitly name or contrast sibling tools such as delete_range or insert_rows.

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?

The description gives no guidance on when to use this tool versus alternatives like delete_range, delete_sheet_columns, or insert_rows. It also omits prerequisites or conditions such as confirming a destructive operation or using dry_run first.

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