Skip to main content
Glama

inspect_deck

Retrieve a deck overview—slide dimensions, theme colors and fonts, plus every slide’s number, ID, and shape count—to map presentation structure before inspecting individual slides.

Instructions

Deck overview: slide dimensions, theme (colors + fonts), and all slides with slide number (1-based), ID, and shape count. Use as the first call to understand deck structure. Theme is cached after the first call. For shape details, follow up with scan_slide or inspect_slide on specific slides. For available layouts, use inspect_layouts.

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

Input Schema

NameRequiredDescriptionDefault
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.4/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 full burden, and it discloses non-obvious behavior: the theme is cached after the first call (affecting freshness of subsequent results) and slide numbers are 1-based. It does not explicitly state that the tool is read-only or whether very large decks are truncated, which are minor residual gaps.

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 output contents are front-loaded in the first sentence, then the sequencing guidance, then the caching caveat, then sibling routing. Every clause carries information; nothing is 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 read-only inspection tool with no output schema, the description does a good job enumerating the returned fields and the caching behavior. It could be slightly more complete by noting whether results are limited on very large decks or what happens with an invalid presentationId, but nothing essential to calling it 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?

There is a single parameter at 100% schema description coverage, and the schema already explains that presentationId comes from list_presentations and is optional when only one presentation is connected. The description adds no parameter-level guidance beyond that, so the schema does the work and 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?

The description opens with a concrete verb+resource framing ('Deck overview') and enumerates exactly what is returned: slide dimensions, theme colors and fonts, and every slide with 1-based number, ID, and shape count. This is clearly distinguishable from siblings like scan_slide or inspect_layouts, which cover shape detail and layouts respectively.

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?

It states an explicit sequencing rule ('Use as the first call to understand deck structure') and names the alternatives for each follow-up need: scan_slide or inspect_slide for shape details, inspect_layouts for layouts. An agent has no ambiguity about when to pick this tool instead of its siblings.

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