Deckary MCP tool reference
Reference for the five saved-deck tools and five live PowerPoint tools exposed by Deckary's remote MCP server.
Last verified: 2026-09-04
Deckary exposes ten MCP tools: five for saved Web Builder decks and five for explicitly shared live PowerPoint presentations. Discovery and read tools are non-destructive. Authoring tools validate current artifact truth before applying a change. The connected client's tool schema is authoritative for exact fields and limits.
Saved Web Builder tools#
| Tool | Purpose | Main inputs | Mutation behavior |
|---|---|---|---|
list_decks | List the signed-in user's saved decks | Optional query and limit | Read-only |
read_deck | Read revision, outline, theme, and selected editable scenes | deckId; optional slideIds | Read-only |
render_consulting_visual | Prepare a validated theme-bound consulting visual | deckId, recipe, configuration, and alt text | May idempotently add one reusable deck asset; never changes deck content or revision |
render_slides | Render up to four exact 960×540 slide PNGs | deckId, one to four slideIds | Read-only |
author_deck | Create or revise supported presentation content | deckId, semantic program | Writes against the current deck revision |
The normal sequence is list_decks → read_deck → optional rendering or visual preparation → author_deck. Reuse the latest revision returned by a successful call.
Live PowerPoint tools#
| Tool | Purpose | Main inputs | Mutation behavior |
|---|---|---|---|
list_live_presentations | List active PowerPoint sessions explicitly shared from the add-in | None | Read-only |
read_live_presentation | Read current slide handles, outline, layouts, theme, and requested scenes | Session ID, connection generation, expected artifact version; optional slide handles and layout IDs | Read-only; may return newer current truth |
inspect_live_objects | Inspect rich text, frames, tables, charts, and exact shape appearance | Current session/version plus 1–10 shape handles; optional table range | Read-only; may return newer current truth |
render_live_slides | Render up to four slides through Office's native renderer | Current session/version, slide handles, optional visual detail | Read-only; may return newer current truth |
author_slide | Create or patch exactly one live slide with semantic Slide DSL | Current session/version, program, optional visual detail | Non-idempotent write with fresh Office compare-and-swap |
For live calls, reuse the latest sessionId, connectionGeneration, and artifact version returned by any successful tool call. Observation calls can recover newer truth. A write is rejected when the expected version is no longer current.
Read and inspection limits#
read_deckaccepts up to ten selected saved-deck slide IDs.render_slidesandrender_live_slidesaccept up to four slides.read_live_presentationaccepts up to ten slide handles and up to four explicit layout IDs.inspect_live_objectsaccepts one to ten current shape handles.- Oversized native tables use a bounded zero-based
tableRangewhen the first inspection reportsrangeRequired. visualDetail=atlasis available for exactly one live slide when close-up inspection is necessary.
Limits keep tool responses bounded for an external model. Prefer targeted reads to repeatedly requesting an entire presentation.
Authoring guarantees#
Saved-deck authoring is revision-bound. Live authoring performs a fresh Office capture and compare-and-swap immediately before mutation. Complete validation failures and live version conflicts produce zero mutation.
For author_slide, treat applied: true as terminal success and settlement_unknown as non-retryable until current presentation truth has been read. This prevents a duplicate mutation when the connection result is uncertain.
Scope-dependent tool discovery#
The decks:edit OAuth permission exposes the five saved-deck tools. The separate live-powerpoint:edit permission enables the five live tools. A live tool still needs an active add-in sharing session after authorization.
If the expected tools are missing, reconnect and approve the required scope, then follow Troubleshooting.