Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_named_range

Destructive

Remove a workbook-level or sheet-scoped named range from an Excel .xlsx file, with an optional dry run to preview the deletion before applying changes.

Instructions

Delete a workbook-level or sheet-scoped named range.

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>",
      "name": "<name>"
    },
    "name": "delete_named_range"
  }
}

Input Schema

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

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.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, so the safety profile is carried structurally. The description adds only the scope distinction and says nothing about irreversibility, error behavior when the name is absent, or what a dry run reports — the key behavioral affordances an agent needs for a destructive call.

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?

A single front-loaded sentence with no filler; the verb and its object appear immediately. Nothing is redundant or padded.

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 four parameters, 25% schema coverage, and no output schema, the description is too thin. It omits dry_run, missing-range behavior, and confirmation/error semantics, leaving the agent to guess on the risky parts of the call.

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 25% (only filepath is documented), so the description must compensate. It partially explains scope_sheet by contrasting 'workbook-level' versus 'sheet-scoped', but leaves 'name' matching semantics and especially 'dry_run' — the most important parameter for a destructive tool — entirely 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 and resource (delete a named range) and adds that both workbook-level and sheet-scoped ranges can be targeted. It does not explicitly route against siblings like create_named_range, inspect_named_range, or list_named_ranges, but 'named range' is specific enough that confusion is unlikely.

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 never says when to use this versus list_named_ranges/inspect_named_range first, nor any preconditions (must the range exist, must the sheet exist, does a dry run need to precede it). Usage is only inferable from the verb itself.

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