Skip to main content
Glama

read_speaker_notes

Read speaker notes from PowerPoint slides as plain text, optionally filtered by slide range, using full-deck OOXML parsing when Office.js lacks a notes API.

Instructions

Read speaker notes from slides. Uses full-deck export (cached by revision) to parse notes from OOXML — Office.js has no notes API. Returns plain text per slide.

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": "read_speaker_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideRangeNoSlide numbers, 1-based, e.g. "1", "1-5", "2,4,7". Omit to read all slides.
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, e.g. \"0\", \"0-5\", \"2,4,7\". Omit to read all slides."New value: +"Slide numbers, 1-based, e.g. \"1\", \"1-5\", \"2,4,7\". Omit to read all slides."
  2. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the mechanism (full-deck export cached by revision) plus the reason (Office.js lacks a notes API). It omits operational consequences: the export may be slow on large decks, notes may be empty, and no permission or caching-invalidation behavior is described.

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?

Three short sentences, front-loaded with the action and closing with the return value; every sentence carries information. Minor redundancy between "read speaker notes" and "parse notes from OOXML" keeps it just below top marks.

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 two-optional-parameter read tool with no output schema, the description covers purpose, mechanism, and return format adequately. The remaining gap is edge-case behavior, such as slides without notes or how cached revisions are invalidated.

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 slideRange and presentationId are already fully documented with formats and examples. The description adds no parameter-level meaning beyond the schema, making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read speaker notes from slides" gives a specific verb and resource, and the closing sentence defines the output shape (plain text per slide). The read verb implicitly contrasts with the sibling edit_speaker_notes, though that alternative is never named explicitly.

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?

Usage is only implied: an agent can infer this is the tool for retrieving notes, but the description never states when to prefer it over read_deck_text or how it relates to edit_speaker_notes. No prerequisites, no exclusions, no alternative routing.

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