KitchenSink4PPT

Overview Schema Source Related Servers Discussions Admin

Get Slide Info

get_slide_info

Read-only

Retrieves a slide's layout, hidden flag, notes presence, and every shape's ID, name, kind, geometry in inches, placeholder type, and text preview. These shape IDs act as addresses for editing tools.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds value beyond that: it discloses pagination behavior ('page' block with omitted count and next offset), the durable shape-id convention, and the live-save caveat (UNSAVED until live_save). This is useful behavioral context not present in the annotations.

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?

Front-loaded with the core return semantics in the first sentence, then narrows to parameter nuance. The final live-mode sentence is dense and slightly run-on, but still conveys three distinct modes in a compact way; nothing is wasted.

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?

An output schema exists, so return-value documentation is covered by the structured field. Given the tool's complexity (pagination, multi-mode live handling, shape-id addressing), the description is thorough enough for an agent to invoke it correctly; only minor polish around the live sentence would push it higher.

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 carries the full burden and delivers: it explains the 'slide' parameter (0-based index or {"slide_id": N}), the limit/offset pagination semantics, and the live parameter's three modes in detail. Only file_path is left to self-evidence.

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?

States a specific verb ('get') + resource ('slide info') and enumerates exactly what is returned: durable slide_id, layout, hidden flag, notes presence, and every shape's id/name/kind/geometry/placeholder/text. Distinguishes from get_presentation_view, which is explicitly named as the all-slides counterpart.

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?

Routes the user to get_presentation_view for the all-slides use case and explains the live parameter's role when the file is locked by PowerPoint. Gives clear context for when to call this tool, though it does not state explicit exclusions for every sibling (e.g., apply_edits).

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