KitchenSink4PPT

Overview Schema Source Related Servers Score Discussions Admin

get_slide_info

Read-only

Get a slide's full details: durable ID, layout, hidden flag, notes presence, and every shape with ID, name, geometry, placeholder type, and text preview. Use these shape IDs to edit the slide.

Instructions

One slide in depth: durable slide_id, layout, hidden flag, notes presence, and every shape with id, name, kind, geometry in inches, placeholder type, and text preview. Shape ids here are the addresses every editing tool takes; edit what it lists via the graphics pack. slide: 0-based index or {"slide_id": N}. Budgeted: a crowded slide returns a "page" block with the omitted count and next offset. All slides: get_presentation_view. 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.

Input Schema

TableJSON Schema

Name	Required	Default
`live`	No	auto
`limit`	No
`slide`	Yes
`offset`	No
`file_path`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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"
+}

removedInput schema / properties / slide / title
```
Removed value: -"Slide"
```

First observedv1.0.0Aug 31, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The description states that "live='auto' edits the open PowerPoint copy" while the annotations declare readOnlyHint=true. This directly contradicts the read-only annotation and could mislead an agent into thinking the tool mutates the presentation. Despite other useful behavioral disclosures, the contradiction is severe.

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 front-loaded with a clear summary, then adds shape-id relevance, slide addressing, pagination, and live-mode behavior. It is dense but each clause contributes useful information. A bit of restructuring or bullets could improve skimmability, but it is not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers return fields, shape IDs, pagination, and sibling routing well, and an output schema is present. However, the live-mode 'edits' contradiction creates a significant completeness problem: an agent cannot safely infer whether this tool has side effects, which undermines the otherwise rich context.

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%, so the description must carry parameter meaning. It explains slide input as '0-based index or {"slide_id": N}' and describes live modes in detail. It also gives contextual meaning to limit/offset through the budgeted page-block explanation, though file_path and exact numeric semantics are left implicit.

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 names the tool's purpose: retrieve detailed information about a single slide, listing concrete fields like durable slide_id, layout, hidden flag, notes presence, and shape geometry. It also distinguishes itself from siblings by explicitly pointing to get_presentation_view for all slides.

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 provides explicit routing: 'All slides: get_presentation_view.' It also explains the live parameter modes, locked-file behavior, and pagination via 'page' block with omitted count and next offset, giving the agent actionable guidance on when and how to use the tool.

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