Skip to main content
Glama

show_slide

Navigate a live presentation to a specified slide so users can watch edits happen or follow a deck step by step; call before editing to keep changes visible.

Instructions

Bring a slide into view in the live presentation (navigates the user to that slide). Call this BEFORE editing a slide so the user can watch the changes happen; also useful to walk the user through a deck slide by slide.

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": {
      "slide": "<slide>"
    },
    "name": "show_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideYesSlide number, 1-based (slide 1 = first slide).
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • addedInput schema / properties / slide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide).",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index to show.",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex"
      -]New value: +[
      +  "slide"
      +]
  2. First observedv0.6.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does disclose the crucial non-obvious side effect: this mutates the user's live view state by navigating them to a slide. It omits session prerequisites (what happens if no live presentation is connected) and whether it errors or is a no-op, which keeps it from a 5.

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, zero waste: the primary action and its user-visible effect are front-loaded in parentheses, followed by the usage guidance. Every clause earns its place.

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 simple two-parameter navigation tool with no output schema and no annotations, the description covers purpose, timing, and the main side effect adequately. The only meaningful gap is failure behavior when no live session is active.

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% — both 'slide' (1-based) and 'presentationId' are fully documented in the schema, including the note that presentationId is optional with a single connected presentation. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Bring a slide into view') and scopes it precisely to 'the live presentation,' which separates it from the inspection siblings (inspect_slide, preview_deck, screenshot_slide) that don't move the user's view. It stops short of naming a sibling explicitly, so it's clear but not fully differentiated by name.

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?

Gives two concrete when-to-use conditions: call before editing so the user can watch changes, and for slide-by-slide walkthroughs. There are no when-not conditions or named alternatives (e.g., use preview_deck when no live session exists), which keeps it below a 5.

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