Skip to main content
Glama

manage_speaker_notes

Read, write, or clear speaker notes on any slide to keep presenter cues out of the audience view.

Instructions

Read, write or clear a slide's speaker notes.

Notes belong in the notes pane, never in a text box on the slide itself — a "notes" textbox is visible to the audience during the presentation.

operation: "get" return the notes for slide_index, or for every slide when slide_index is omitted; "set" replace the notes on slide_index with text; "clear" remove the notes from slide_index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
operationYes
slide_indexNo
presentation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.6.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations provide only a title, so the description carries the behavioral transparency burden. It does so by disclosing that get returns notes, set replaces notes, and clear removes notes, including the get-all behavior when slide_index is omitted. It does not discuss permissions or side effects, but the core operation semantics are transparent.

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 compact and well organized: a concise summary line, one valuable usage warning about notes pane versus text box, then a clear operation list. Every sentence adds information and the structure makes the behavior easy to scan.

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?

The description covers the essential call-shaping details: operation values, text semantics, slide_index optionality, and get-all behavior. It is slightly implicit that set and clear effectively require slide_index even though the schema marks it optional; an explicit statement there would make the description fully complete.

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

Parameters5/5

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

Schema description coverage is 0% and operation has no enum, yet the description fully defines the valid operation values and their parameter behavior. It explains what text does for set, what slide_index does for get/set/clear, and how omitting slide_index affects get. This strongly compensates for the schema gaps.

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 opens with a specific verb/resource combination: 'Read, write or clear a slide's speaker notes.' It also distinctly clarifies that speaker notes belong in the notes pane, not in a slide text box, which separates this tool from text-manipulation siblings.

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?

The description gives clear per-operation guidance and emphasizes the notes-pane distinction, helping an agent choose this tool for speaker notes rather than visible slide text. It does not explicitly name sibling alternatives or say 'use X instead,' but the context is sufficient for correct routing.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/photonn/dial-pptx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server