KitchenSink4PPT

Overview Schema Source Related Servers Score Discussions Admin

get_text

Read-only

Extract plain text from PowerPoint slides in reading order, including table cells and speaker notes, with optional scoping by slide and paging for large decks.

Instructions

Plain text of the deck in reading order: shapes in spTree order, table cells tab-joined, fields rendering their cached text. scope: None for all slides, a 0-based index, {"slide_id": N}, or a list; include_notes=True appends speaker notes. Budgeted, paging in whole slides: slide_count stays the deck's true total and a "page" block gives the omitted count and the next offset; limit/offset page explicitly. Rendered-appearance checks live in the assembly-export pack. live='auto' edits the open PowerPoint copy when the file is locked by it (UNSAVED until live_save, com pack); 'force' targets the open session; 'off' refuses locked files. For edit anchors, use get_presentation_view.

Input Schema

TableJSON Schema

Name	Required	Default
`live`	No	auto
`limit`	No
`scope`	No
`offset`	No
`file_path`	Yes
`include_notes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.2.1Sep 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "type": "integer"
+}

First observedv1.0.0Aug 31, 2026

TDQS

A4/5.0

Behavior1/5

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

The description says 'live=auto edits the open PowerPoint copy when the file is locked by it' and mentions UNSAVED changes until live_save, which directly contradicts the annotation readOnlyHint=true. This is a serious inconsistency: a read-only tool should not be editing the target file.

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 purposeful: it front-loads the primary purpose and then systematically covers parameters and special behaviors. The main drawback is heavy jargon such as 'com pack' and 'assembly-export pack' that assumes domain knowledge, but there is no filler or repetition.

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?

The description covers reading order, scoping, notes, paging, live behavior, and sibling routing, while the output schema handles return shape. It is nearly complete, but unexplained domain-specific terms and the unresolved contradiction with readOnlyHint prevent a perfect score.

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 0%, so the description carries the full burden for parameter semantics. It covers scope (None, 0-based index, slide_id dict, list), include_notes, limit/offset paging behavior, and live values ('auto', 'force', 'off'). Only file_path is left implicit, but its meaning is self-evident.

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 clearly states the tool returns 'Plain text of the deck in reading order' and specifies the ordering rules without ambiguity. It also differentiates itself from siblings by pointing to get_presentation_view for edit anchors and noting that rendered-appearance checks live elsewhere.

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 explicitly describes scope options, include_notes behavior, limit/offset paging, and live mode semantics. It also provides an exclusion: for edit anchors, use get_presentation_view. This gives an agent clear, actionable guidance on when and how to invoke the tool.

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