Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Move Range

move_range
Destructive

Move a cell range to a new anchor on the same sheet, rewriting formulas, names, formatting, and validations so references follow the cells.

Instructions

Move a rectangle to a new anchor on the same sheet, rewriting every formula, name, conditional format, validation, table ref, and merge that pointed into the source so references follow the cells (Excel move semantics). A cross-sheet destination refuses (copy_range then clear_range instead); cells at the destination are overwritten. A hazardous workbook refuses unless allow_loss is true. Auto-backup to .ks4xl-backups; atomic verified save. Refuses while open in Excel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destYesWhere the result lands (its top-left cell).
pathYes
sheetNo
backupNo
sourceYesThe range to read from.
allow_lossNo
verify_comNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed4 schema fields changedv1.1.0
    • addedInput schema / properties / dest / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "object"
+  }
+]
    • addedInput schema / properties / dest / description
      Added value: +"Where the result lands (its top-left cell)."
    • addedInput schema / properties / source / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "object"
+  }
+]
    • addedInput schema / properties / source / description
      Added value: +"The range to read from."
  3. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already mark this destructive, and the description adds substantial beyond-schema behavior: rewriting formulas, names, conditional formats, validation, table refs, and merges; overwriting destination cells; requiring allow_loss for hazardous workbooks; auto-backup; atomic verified save; and refusing while open in Excel. No contradiction with annotations.

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?

Every clause carries a distinct, important fact: core semantics first, then restrictions, safety, backup/save behavior, and Excel lock refusal. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex destructive move operation, the description is thorough: it covers preconditions (same sheet, not open in Excel), side effects (reference rewriting, overwriting), safety (allow_loss, backup, atomic save), and failure modes. A return-value contract is absent, but the behavioral and safety context is strong enough for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 29%, so the description must compensate. It does contextualize allow_loss and backup behavior and clarifies the same-sheet constraint and destination overwrite, but path, sheet, verify_com, and the backup parameter itself are left mostly to inference from their names. It partially compensates but not fully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation—moving a rectangle to a new anchor on the same sheet—and captures the core Excel-move semantics of rewriting references. It is clearly distinguishable from siblings like copy_range and clear_range, and even names the alternative approach for cross-sheet moves.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says cross-sheet destinations are refused and routes to 'copy_range then clear_range instead'. It also gives refusal conditions for hazardous workbooks and while open in Excel, so an agent knows when this tool does and does not apply.

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