Skip to main content
Glama
KitchenSink4AI

KitchenSink4Word

by KitchenSink4AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Cells

set_cells
DestructiveIdempotent

Write multiple Word table cells in a single call using scattered edits or a 2D block, with options for nested tables, change tracking, and atomic backup.

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 nested table in that host cell (edits mode only). track records changes by author. Cell TEXT only: shading, bold and alignment are format_cells, widths and repeat-header set_table_properties (media-forms). Live (plain edits only) refuses vertical merges; file mode is merge-aware. Auto-backup; atomic save. Batches: apply_edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
liveNoauto: file or live; force: live; off: refuseauto
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. Changed2 schema fields changedv2.2.1
    • addedInput schema / properties / live / description
      Added value: +"auto: file or live; force: live; off: refuse"
    • addedInput schema / properties / live / enum
      Added value: +[
+  "auto",
+  "force",
+  "off"
+]
  2. 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"
+]
  3. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / live
      Added value: +{
+  "default": "auto",
+  "type": "string"
+}
  4. First observedv1.2.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds valuable context: 'Auto-backup; atomic save' reveals persistence guarantees, 'track records changes by author' indicates change-logging behavior, and 'Cell TEXT only' declares a hard constraint. It also explains live vs. file merge behavior. These insights go beyond the annotations and help the agent anticipate side effects. Not quite a 5 because it doesn't fully detail failure modes or what happens on validation errors, but it is strong.

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 compact. It packs multiple distinct facts into a few sentences using semicolons and parentheticals, front-loading the core purpose. There is minimal fluff and every sentence adds information. It is slightly overloaded with mode syntax inline (e.g., 'block={origin:{row, cell}, values:[[...]]}') but remains readable. A 4 because it could be broken into clearer bullets for extreme readability, yet it is far from verbose.

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 tool with 9 parameters and low schema coverage, the description covers the essential context: modes, required parameters implied by examples, alternatives, limitations, live/file semantics, backup and atomicity, and batching. An output schema exists, so return values need no explanation. The agent has virtually everything needed to call it correctly, including edge cases like vertical merge refusal. This is a model description for a complex tool.

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?

Schema description coverage is only 11%, so the description must compensate. It does: it explains the structure of 'edits' as [{row, cell, text}], 'block' as {origin, values}, and 'nested' as {row, cell, index}. It also clarifies that 'track' records changes by author and that 'live' has mode semantics. This provides meaning beyond the bare type definitions, though it doesn't exhaustively document every field in the array/object parameters (some nuance remains in the schema).

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.' It clearly distinguishes this from sibling tools by explicitly stating what it does NOT do (formatting via format_cells, properties via set_table_properties) and naming the batch alternative (apply_edits). An agent immediately knows the scope and how it differs from other cell/table tools.

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 gives concrete when-to-use and when-not-to-use guidance: it names format_cells for shading/bold/alignment, set_table_properties for widths and repeat-header, and apply_edits for batches. It also clarifies mode-specific behavior (live refuses vertical merges; file mode is merge-aware), so the agent knows which mode to choose based on the need.

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