Skip to main content
Glama
KitchenSink4AI

io.github.nometalalchemist/kitchensink4xl

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

set_cell

Set a single cell in an Excel workbook by location, accepting numbers, text, booleans, or formulas. Uses verified saves with backup to prevent data loss.

Instructions

Write a single cell addressed by a location object. A string beginning with '=' is ALWAYS stored as a formula (there is no literal escape), normalized so modern functions do not land as #NAME? and flagged to recalculate on open; anything else is a literal. A hazardous workbook refuses unless allow_loss is true. Auto-backup: prev/anchor slots in .ks4xl-backups (backup=false skips rotation); atomic verified save, restored on failed verify. Refuses while open in Excel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
sheetNo
valueYesA cell value: text, a number, a boolean, or null to clear. A string beginning with '=' is stored as a formula.
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. Changed3 schema fields changedv1.1.0
    • addedInput schema / properties / location / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "object"
+  }
+]
    • addedInput schema / properties / value / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / value / description
      Added value: +"A cell value: text, a number, a boolean, or null to clear. A string beginning with '=' is stored as a formula."
  3. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

The description goes far beyond the sparse readOnlyHint=false annotation. It discloses formula normalization, the lack of literal escapes for strings beginning with '=', recalculation flags, hazardous workbook refusal, backup rotation behavior, atomic verified saves with rollback, and refusal while the workbook is open in Excel. This is rich, non-obvious behavioral context.

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 adds necessary operational detail. The core purpose is front-loaded, followed by formula behavior, safety caveats, backup semantics, and the Excel lock refusal. There is no filler or repetition.

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 mutation tool with 7 parameters and no output schema, the description covers most critical behavior: formulas, backups, allow_loss, and workbook lock. It does not explain verify_com or return/verification outcomes, but the atomic-verified-save mention partially covers the verification concept. Overall it is strong but not fully exhaustive.

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 14%, so the description carries heavy weight. It does add meaning for value ('=' means formula, otherwise literal), location, backup=false skip behavior, and allow_loss. However, it leaves verify_com unexplained and does not clarify path or sheet semantics, so it only partially compensates for the low schema coverage.

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 'Write a single cell addressed by a location object,' which names the exact action, target resource, and scope. It clearly distinguishes this tool from range-oriented siblings like write_range or set_cells by emphasizing a single cell.

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 gives clear context for when to use this tool: writing a single cell, including formula/literal handling and safety conditions like allow_loss and Excel lock refusal. It does not explicitly name sibling alternatives or state 'use X instead for ranges,' but the single-cell framing is a solid implicit guide.

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