Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

move_range

Move a range to a new anchor on the same sheet, rewriting formulas, names, and references so they follow the moved cells. Refuses cross-sheet moves; overwrites destination 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.6/5.0
Behavior5/5

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

The description reveals extensive behavioral details beyond the minimal readOnlyHint: false annotation: rewriting all reference types, overwriting destination cells, refusing hazardous workbooks without allow_loss, auto-backup, atomic verified save, and Excel lock refusal. There is no contradiction with the annotation; the mutation implied by 'move' aligns with readOnlyHint false.

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?

The description is dense but every sentence earns its place: purpose first, then reference-rewriting behavior, then constraints and fallback, then safety and persistence details. No filler or redundant restatement of the name or input schema.

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

Completeness4/5

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

For a complex mutation tool with no output schema and minimal annotations, the description is impressively complete: it covers same-sheet scope, overwrite semantics, cross-sheet alternative, hazard handling, backup, save verification, and Excel lock refusal. The only notable omission is what the tool returns after a successful move, plus a couple of parameters (verify_com) remain ambiguous.

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 description coverage is only 29%, so the description must compensate for the missing parameter documentation. It does add context for allow_loss ('hazardous workbook refuses unless allow_loss is true') and backup ('Auto-backup'), and implies the sheet parameter via 'same sheet', but path, sheet, and verify_com remain largely unexplained. The description partially compensates but does not fully resolve the parameter semantics gap.

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 verb and resource: 'Move a rectangle to a new anchor on the same sheet' with Excel move semantics. It clearly distinguishes this from copy_range and clear_range by naming them as alternatives. The purpose is unambiguous and immediately scoped.

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?

The description explicitly says cross-sheet destinations are refused and instructs to use copy_range then clear_range instead. It also states hazard conditions, allow_loss behavior, and refusal while open in Excel, giving an agent concrete conditions for when to use this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools