KitchenSink4Word

Overview Schema Source Related Servers Score Discussions Admin

create_table

Create formatted Word tables from 2D string data, with single-line borders and a bold header row. Specify location, width, and backup options for precise document placement.

Instructions

Create a table from 2D string data with single-line borders and a bold repeating header row (header_row=False for none). location is the standard location object ({paragraph}, {after_heading}, {outline}, {search}, {anchor}); omit it to append at the document end; position 'after' only. To build a table from a CSV or JSON file use import_table (protection-io pack). Auto-backup: prev/anchor slots in .ks4w-backups (backup=False skips rotation only); atomic validated save. Refuses documents open in Word.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`backup`	No
`location`	No
`width_pt`	No
`file_path`	Yes
`header_row`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.0.0Sep 4, 2026

removedInput schema / properties / after_anchor

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

removedInput schema / properties / after_index

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

removedInput schema / properties / at_end

Removed value: -{
-  "default": false,
-  "type": "boolean"
-}

addedInput schema / properties / location

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedv1.2.1Aug 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With only readOnlyHint=false in annotations, the description carries the behavioral burden and does so thoroughly. It discloses the backup rotation behavior, backup=False semantics, atomic validated save, bold header default, and the refusal to operate on documents open in Word.

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 ordered: purpose first, then formatting, placement, file-import alternative, save/backup behavior, and failure condition. Every sentence adds new information and no filler is present.

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?

Given the output schema exists and annotations are minimal, the description supplies the required context: input format, options, insertion behavior, safety/backup behavior, and error condition. An agent can reliably decide whether and how to call create_table from this text alone.

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 0%, but the description compensates for most parameters: data as 2D strings, header_row toggle, location object forms/omission semantics, and backup flag behavior. The only parameter left unexplained is width_pt, whose effect on table layout is not 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: 'Create a table from 2D string data' and clarifies the exact formatting (single-line borders, bold repeating header). It also names import_table as the alternative for file-based input, distinguishing this tool from the CSV/JSON import path.

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?

It explicitly tells the agent when to use this tool (2D string data) versus import_table (CSV/JSON files). It also specifies placement rules, the 'after' positioning constraint, and the Word-open refusal, so the agent knows when the call will fail.

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