Skip to main content
Glama

scan_slide

List shape IDs, types, and positions on slides with slide dimensions to identify shapes before editing. Use inspect_slide for text content and fills.

Instructions

Lightweight shape scanner (~40 tokens/shape): lists shape IDs, types, and positions on slides, plus slide dimensions. Supports slideRange for multiple slides. For text content and fills, use inspect_slide instead.

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": {
      "slideRange": "<slideRange>"
    },
    "name": "scan_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
shapeTypeNoFilter by shape type: "Placeholder", "TextBox", "GeometricShape", "Graphic", "Picture", etc.
slideRangeYesSlide numbers, 1-based, e.g. "1", "1-5", "2,4,7". Single number or range.
namePatternNoGlob-style filter on shape name, e.g. "Title*", "*_source", "Card*_bg". Case-insensitive.
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 scan, e.g. \"0\", \"0-5\", \"2,4,7\". Single index or range."New value: +"Slide numbers, 1-based, e.g. \"1\", \"1-5\", \"2,4,7\". Single number or range."
  2. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present the description must carry the behavior load, and it does disclose the cost model (~40 tokens/shape) and the deliberate omission of text and fills, implying a read-only inspection. It does not explicitly state read-only semantics, permission requirements, or failure behavior for invalid slide numbers.

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 capability and cost, followed by the routing rule. No filler or restatement of the name.

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?

There is no output schema, yet the description enumerates the return fields (shape IDs, types, positions, slide dimensions), which covers what an agent needs to consume results. Only error/edge-case behavior and explicit read-only status are absent, which is minor for a lightweight scanner.

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 all four parameters are already documented in the schema. The description only adds that slideRange accepts multiple slides, which the schema itself already conveys with its example formats; no extra meaning is added for shapeType, namePattern, or presentationId.

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 concrete verb-plus-resource ("shape scanner ... lists shape IDs, types, and positions on slides, plus slide dimensions") and states the exact payload, so an agent knows precisely what it returns. It also distinguishes itself from inspect_slide by scope (shape metadata vs. text content and fills).

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?

It routes the agent away from this tool for text/fill needs by naming the alternative: "For text content and fills, use inspect_slide instead." It also notes slideRange handles multiple slides. It stops short of stating positive triggering conditions (e.g., 'use first to get shape IDs before format_shapes'), but the exclusions are explicit.

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