KitchenSink4Word

Overview Schema Source Related Servers Discussions Admin

Get Text

get_text

Read-only

Retrieve Word document paragraphs with styles, start/end indexes, and filters. Optionally include textboxes and read equations from live or file-based documents.

Instructions

Read body paragraphs as [{index, text, style, ...}] with effective styles. start/end slice by paragraph index (0-based, end EXCLUSIVE); contains filters. include_textboxes=True appends text-box content as labeled extras, body indices untouched; textbox=true (or {"index": n}) returns ONLY text-box content, with the box_index set_textbox_text (media-forms pack) takes; file-mode only. Open documents read live, same shape. Equations read via list_elements type='equations'. Read-only. Orientation: get_document_view.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end`	No
`live`	No	auto: file or live; force: live; off: refuse	auto
`start`	No
`textbox`	No
`contains`	No
`file_path`	Yes
`include_textboxes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.2.1Sep 24, 2026
- 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"
+]
```

Changed1 schema field changedv2.0.0Sep 4, 2026

addedInput schema / properties / textbox

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

Changed5 schema fields changedv1.6.1Aug 31, 2026

addedInput schema / properties / include_textboxes

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / live

Added value: +{
+  "default": "auto",
+  "type": "string"
+}

addedOutput schema / properties / result / anyOf

Added value: +[
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

removedOutput schema / properties / result / items
```
Removed value: -{}
```
removedOutput schema / properties / result / type
```
Removed value: -"array"
```

First observedv1.2.1Aug 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses rich behavioral details: slicing semantics with 0-based end-exclusive indices, contains filtering, include_textboxes behavior, textbox-only mode with box_index expectations, file-mode restrictions, and live-document behavior. This substantially exceeds what annotations provide.

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 and information-rich, with the primary return shape front-loaded. Some clauses are terse to the point of requiring careful parsing, but every sentence contributes meaningful guidance with no filler.

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 the complexity of the tool, the description covers the return shape, parameter semantics, mode differences, textbox special cases, and sibling routing. An agent has enough context to invoke the tool correctly in both file and live scenarios.

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 description coverage is only 14%, so the description carries the parameter-documentation burden. It explains start/end indexing, end-exclusive slicing, contains filters, include_textboxes vs textbox modes, and live/file behavior. This compensates well for the sparse schema descriptions.

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: 'Read body paragraphs as [{index, text, style, ...}] with effective styles.' It clearly distinguishes itself from siblings by noting that equations are handled by list_elements and orientation by get_document_view, so the tool's scope is unambiguous.

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 provides clear context for when to use this tool and routes alternatives: equations go through list_elements, and orientation goes through get_document_view. It also explains mode-specific behavior for live vs file documents, though it does not enumerate all sibling exclusions explicitly.

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