KitchenSink4Word

Overview Schema Source Related Servers Discussions Admin

Get Table

get_table

Read-only

Reads an entire Word table, returning every cell's text, merge info, and column widths. Handles nested tables; use for extracting full table data before editing.

Instructions

Read one table in full: every cell's text, the merge map, and column widths. table_index is 0-based among body-level tables in document order. has_merges=false returns rows of strings; has_merges=true returns {text, grid_span, vmerge} cells. For a nested table pass nested={row, cell, index} addressing the host cell (index picks among several, default 0). Write with set_cells; shade with format_cells; widths and repeat-header set_table_properties; reshape with modify_table_structure (media-forms pack). Read-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`nested`	No
`file_path`	Yes
`table_index`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Sep 4, 2026

addedInput schema / properties / nested

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

First observedv1.2.1Aug 27, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already assert readOnly/openWorld behavior; the description goes beyond by disclosing the two output modes selected by has_merges and the nested-table addressing convention. It also explicitly repeats 'Read-only,' reinforcing the annotation.

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?

Every sentence carries information: purpose, return variants, nested addressing, and sibling routing. It is front-loaded with the core capability and stays structured without redundancy.

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 read tool with an output schema and readOnly/openWorld annotations, the description supplies the missing contextual semantics: indexing rules, merge-mode behavior, nested-table invocation, and which sibling tools handle writes/shading/structure changes. Nothing needed for correct invocation is left undocumented.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full param-documentation burden. It explains table_index as 0-based among body-level tables in document order and fully specifies the nested object shape and defaults, which the bare schema does not convey.

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 precise verb-resource pair ('Read one table in full') and enumerates exactly what is returned (cell text, merge map, column widths), which distinguishes it from sibling read tools like get_text or get_document_view.

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?

It gives concrete conditions: use has_merges for merged-cell data and nested for nested tables, and it routes mutations to sibling tools (set_cells, format_cells, set_table_properties, modify_table_structure). It lacks an explicit contrast with alternative read-only tools, but the table-specific scope is clear enough.

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