Skip to main content
Glama
office-powerpoint-mcp-server

office-powerpoint-mcp-server

Inspect Presentation

inspect_presentation
Read-onlyIdempotent

Extract all presentation content in one call—slide count, layouts, speaker notes, text frames, and table rows—as structured JSON or readable Markdown.

Instructions

Inspect and extract all content from a presentation in a single call.

Returns slide count, layout names, speaker notes, all text frames, and table rows formatted as structured JSON or readable Markdown.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathNoPath to presentation file on disk
output_formatNoFormat of presentation extraction: 'json' or 'markdown'json
presentation_idNoSession ID of open presentation

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context by stating that it returns slide count, layout names, speaker notes, text frames, and table rows in one call. It does not disclose limitations such as large-file behavior or how open-session IDs affect extraction.

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?

The description is two front-loaded sentences with no filler. The first establishes purpose and single-call scope, and the second enumerates the extracted content and output formats.

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?

For a read-only inspection tool with three optional parameters, full schema coverage, annotations, and an output schema, the description is substantially complete. It explains the extraction scope and return content, though it could add a sentence on input-source selection and when this tool is preferred over per-element alternatives.

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 description coverage is 100%, so the schema already documents file_path, presentation_id, and output_format. The description only echoes that output can be structured JSON or readable Markdown and does not add guidance on choosing between file_path and presentation_id. Baseline 3 is appropriate when the schema carries parameter meaning.

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 uses a specific verb and resource: 'inspect and extract all content from a presentation.' It clearly distinguishes extraction from sibling mutation tools such as manage_presentation, add_slide_from_template, and update_table_cells by emphasizing read-only content inspection in a single call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'in a single call' implies this should be used when full presentation content is needed without multiple per-element calls. However, the description does not explicitly say when to prefer this over alternatives or when not to use it, nor does it clarify whether to supply file_path or presentation_id.

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