Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

write_range

Write a rectangular block of values and formulas into an Excel sheet at a specified cell, leaving surrounding content untouched, with automatic backup and verified save.

Instructions

Write a 2D block of values and formulas anchored at the location's top-left cell. data is a list of row lists and must be RECTANGULAR: ragged rows refuse (pad short rows with null, which clears those cells); content outside the block is never touched. Formula strings ('=...') are normalized and flag recalculation. Grid limits and the 200,000-cell write ceiling apply. 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
dataYesRows of cell values, rectangular: every row the same length.
pathYes
sheetNo
backupNo
locationYes
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 / data / description
      Added value: +"Rows of cell values, rectangular: every row the same length."
    • addedInput schema / properties / data / items / items / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / data / items / items / description
      Added value: +"A cell value: text, a number, a boolean, or null to clear. A string beginning with '=' is stored as a formula."
    • addedInput schema / properties / location / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "object"
+  }
+]
  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?

Beyond the readOnlyHint=false annotation, the description discloses substantial behavioral details: ragged rows are refused, null clears cells, formulas are normalized and trigger recalculation, grid limits and a 200,000-cell ceiling apply, hazardous workbooks require allow_loss, auto-backup and atomic verified save occur, and the tool refuses while open in Excel. This is far beyond the annotation and gives agents accurate expectations.

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 compact yet dense, front-loading the core purpose before detailing data constraints, limits, safety, and refusal conditions. Each sentence adds a distinct piece of behavioral information without redundancy.

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?

The description is comprehensive for a mutating tool with no output schema: it covers the write semantics, data shape, safety, backup, and refusal cases. Minor gaps remain around the exact form of location and the sheet/verify_com parameters, but the core invocation requirements are clearly sufficient for an agent to proceed.

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

Parameters4/5

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

With schema description coverage at only 14%, the description compensates for the most complex parameters: data must be rectangular and ragged rows refuse, null clears, location anchors the block at its top-left cell, and allow_loss gates hazardous workbooks. It does not add semantics for path, sheet, or verify_com, but the critical failure-prone parameters are well covered.

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 opens with a specific verb and resource: 'Write a 2D block of values and formulas anchored at the location's top-left cell.' It specifies the block write scope and differentiates itself from single-cell siblings like set_cell by emphasizing the 2D block and 'content outside the block is never touched.'

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

Usage Guidelines4/5

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

The description clearly establishes when this tool is appropriate: for writing rectangular blocks of values/formulas anchored at a cell, with explicit constraints such as refusing ragged rows and refusing in hazardous workbooks unless allow_loss is true. It does not explicitly name sibling alternatives (e.g., set_cell for single cells), so it stops short of full exclusion guidance.

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