Skip to main content
Glama

inspect_slide

Returns every shape on specified slides with text, position, size, fill color, and slide dimensions so you can audit or analyze PowerPoint content in detail.

Instructions

Detailed slide inspector (~80 tokens/shape): returns every shape with text content, positions, sizes, and fill colors, plus slide dimensions. Supports slideRange for multiple slides. For just positions without text/fills, use scan_slide instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slideRange": "<slideRange>"
    },
    "name": "inspect_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideRangeYesSlide numbers, 1-based, e.g. "1", "1-5", "2,4,7". Single number or range.
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • changedInput schema / properties / slideRange / description
      Previous value: -"Slide indices to inspect, e.g. \"0\", \"0-5\", \"2,4,7\". Single index or range."New value: +"Slide numbers, 1-based, e.g. \"1\", \"1-5\", \"2,4,7\". Single number or range."
  2. First observedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral trait: cost (~80 tokens per shape), which matters for a potentially large payload, along with the exact payload contents. It never explicitly states the operation is read-only or what happens with out-of-range slide numbers, so a small gap remains.

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?

Two sentences, front-loaded with the payload description and the token-cost warning, then the range capability, then the sibling pointer. Nothing is redundant or padded.

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?

No output schema exists, and the description does cover the return shape (shapes with text, geometry, fills, plus slide dimensions) adequately for an agent to decide whether it is worth the token cost. It stops short of describing field names or ordering, which leaves some uncertainty about the exact response structure.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented with examples and the presentationId fallback rule. The description only adds that slideRange may span multiple slides, which is marginal on top of the schema's own "1-5" example and does not mention presentationId at all.

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 and resource ('Detailed slide inspector') and enumerates exactly what is returned: every shape with text content, positions, sizes, fill colors, plus slide dimensions. It also explicitly separates itself from scan_slide, so an agent can pick between them without opening a schema.

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?

Names the alternative (scan_slide) and the precise condition that selects it: positions-only, no text or fills. The 'use X instead' routing is explicit rather than implied.

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