Skip to main content
Glama

screenshot_slide

Capture a single slide as a PNG image to visually verify its layout after edits. Use for per-slide visual QA; use deck preview instead of looping over all slides.

Instructions

Slide screenshot (~1000 tokens): captures one slide as PNG image. Use to visually verify layout after changes. Do NOT loop over all slides — use preview_deck instead. WARNING: renders with whatever font the host webview substitutes when the deck font is not system-installed (e.g. Century Gothic) — substituted fonts have different metrics, so text width, overflow and centering judgments from these screenshots are UNRELIABLE. For font-faithful QA export via PowerPoint itself (AppleScript: save pres in POSIX file "/tmp/x.pdf" as save as PDF, then pdftoppm) and measure geometry with Python (PIL pixel measurement) rather than judging by eye.

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

Input Schema

NameRequiredDescriptionDefault
slideYesSlide number, 1-based (slide 1 = first slide), from scan_slide results
widthNoImage width in pixels. Default: 720. Height auto-calculated to preserve aspect ratio unless also specified.
heightNoImage height in pixels. If omitted, auto-calculated from width to preserve aspect ratio.
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), from scan_slide results",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index from scan_slide results",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex"
      -]New value: +[
      +  "slide"
      +]
  2. First observedv0.6.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discharges it: it discloses the cost (~1000 tokens), the rendering mechanism (host webview font substitution), and a concrete failure mode where output judgments are explicitly labeled unreliable. This is behavior an agent could not guess from the schema.

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?

Front-loaded with the core fact and cost, then routing guidance, then the caveat. The embedded AppleScript/pdftoppm workflow is somewhat beyond a tool description, but it is short and directly serves the stated reliability gap, so it earns most of its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, cost, routing, and a non-obvious correctness hazard with a workaround. For a no-output-schema tool with fully documented params, nothing an agent needs in order to call it and interpret its result correctly is missing.

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 slide numbering, width/height defaults, and presentationId are already fully documented in structured fields. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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 ('captures one slide as PNG image') and immediately differentiates itself from preview_deck. An agent knows exactly what this produces without opening the 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 ('visually verify layout after changes'), an explicit when-not-to ('Do NOT loop over all slides — use preview_deck instead'), and a named alternative path for font-faithful QA. Nothing 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.