Skip to main content
Glama

preview_deck

Batch-review all or selected slides with optional thumbnails or text-only output for visual checks and content audits. Use inspect_slide or screenshot_slide to review one slide.

Instructions

Deck preview: batch overview of all/selected slides with optional thumbnails + text. With images: ~900 tokens/slide; text-only (includeImages=false): ~35 tokens/slide. Use for visual review or content audit. Do NOT use to inspect one slide — use inspect_slide or screenshot_slide instead.

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

Input Schema

NameRequiredDescriptionDefault
imageWidthNoThumbnail width in pixels. Default: 480. Height auto-calculated to preserve aspect ratio.
slideRangeNoSlide numbers, 1-based, e.g. "1-6", "2,4,7", "1-3,5,8-11". Omit for all slides.
includeImagesNoInclude slide thumbnails. Default: true. Set false for text-only overview (faster).
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 include, e.g. \"0-5\", \"2,4,7\", \"0-2,5,8-10\". Omit for all slides."New value: +"Slide numbers, 1-based, e.g. \"1-6\", \"2,4,7\", \"1-3,5,8-11\". Omit for all slides."
  2. First observedv0.6.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it quantifies cost (~900 tokens/slide with images vs ~35 text-only), which is exactly the kind of operational context an agent needs before a large batch call. It stops short of stating the read-only nature explicitly or describing the shape of each slide entry in the returned overview, so it is strong but not complete.

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?

Three short sentences, front-loaded with the core purpose, then cost, then routing. Every sentence carries distinct information — no restatement of the tool name or filler.

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 4-parameter, all-optional read tool with no annotations and no output schema, the description covers purpose, cost, and alternatives well. A brief note on what the overview actually returns per slide (number, text, thumbnail) would close the last gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning on top: it quantifies the includeImages tradeoff (~900 vs ~35 tokens/slide), turning a boolean into a decision with measurable cost. slideRange and imageWidth are left entirely to the schema, which already documents them adequately.

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 ("Deck preview: batch overview of all/selected slides") and immediately scopes it to batch rather than single-slide work. The contrast with inspect_slide and screenshot_slide makes it distinguishable from siblings without opening any 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?

Gives explicit when-to-use ("visual review or content audit") and an explicit when-not ("Do NOT use to inspect one slide") with two named alternative tools. Nothing about tool selection is left to inference.

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