Skip to main content
Glama
KitchenSink4AI

KitchenSink4Word

by KitchenSink4AI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

set_cells

Populate multiple table cells in one operation with scattered or block mode; handle merges, tracked changes, and automatic backup for reliable Word document updates.

Instructions

Write many table cells in one call. Modes: edits=[{row, cell, text}] for scattered cells, or block={origin:{row, cell}, values:[[...]]} for a 2D block. nested={row, cell, index} targets a table nested in that host cell (edits mode only). track records tracked changes by author. Live mode (plain edits only) refuses vertical merges; file mode is merge-aware. Auto-backup in file mode (backup=False skips rotation); atomic validated save. Documents open in Word edit live, serialized. For batches, use apply_edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
liveNoauto
blockNo
editsNo
trackNo
authorNoClaude
backupNo
nestedNo
file_pathYes
table_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • addedInput schema / properties / block
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / edits / anyOf
      Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / edits / default
      Added value: +null
    • removedInput schema / properties / edits / items
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • removedInput schema / properties / edits / type
      Removed value: -"array"
    • addedInput schema / properties / nested
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • changedInput schema / required
      Previous value: -[
-  "file_path",
-  "table_index",
-  "edits"
-]New value: +[
+  "file_path",
+  "table_index"
+]
  2. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / live
      Added value: +{
+  "default": "auto",
+  "type": "string"
+}
  3. First observedv1.2.1

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the single readOnlyHint=false annotation, the description discloses substantial behavior: tracked changes by author, live mode restrictions, merge awareness, auto-backup behavior, atomic validated save, and serialization behavior in Word. This gives the agent a strong sense of side effects and constraints without needing to infer them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence adds useful information. It could benefit from bullets or segmentation for readability, yet it remains appropriately sized and opens with the primary purpose. The mode distinctions and caveats are packed in without fluff.

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?

Given the tool's complexity (9 parameters, multiple modes, backup behavior) and the presence of an output schema, the description covers most critical decision points. It explains mode restrictions, backup behavior, and alternative tool routing. Minor gaps remain around the live parameter semantics and author usage, but they are not critical.

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 0% schema description coverage, the description does heavy lifting by explaining the edits, block, and nested parameter shapes with concrete examples. It also clarifies backup=False semantics. Some parameters like author and live are only implicitly covered, but the core complex parameters are well described.

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 many table cells in one call,' which clearly defines the tool's scope. It further distinguishes itself by enumerating modes (edits, block, nested) that map to specific table-write scenarios. This effectively separates it from sibling tools like apply_edits.

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 explicit routing guidance with 'For batches, use apply_edits,' naming the sibling alternative. It also provides mode-specific usage context, such as live mode refusing vertical merges and file mode being merge-aware. However, it does not fully enumerate when not to use set_cells beyond the batch reference.

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