GlideDeck
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
GlideDeck builds zooming presentations: slides are frames on an infinite canvas and the show flies the camera between them. Every tool reads and writes a .glide.json GlideDeck project file, saved immediately, which the user can later open and edit in the GlideDeck app (or with open_in_editor). Workflow: catalog → create_presentation (pick a template that fits the story) → get_presentation to see each slide's placeholder text with element ids → update_elements to replace ALL placeholder text → add_slide with a layout and its text fields for more slides → render_slide to check every slide visually → export_pptx / export_pdf if the user wants PowerPoint or PDF, or export_html for a web page that plays the show in a browser with every effect intact. To show a YouTube, Vimeo or Loom video on a slide, use add_web_video. To start from an existing PowerPoint file, use import_pptx, then arrange_slides to give it a zooming path. Keep slide text short: one idea per slide. HOUSE STYLE: GlideDeck's own look is the Darkroom theme: a flat graphite canvas, bone-white type and ONE signal yellow, with no gradients, glows or glass. Daylight is its light twin (cool white, cobalt accent) for bright rooms and print. Unless the user asks for another look, pass theme "darkroom" (or "daylight") to create_presentation; a blank deck uses Darkroom by itself. Stay inside the theme: short, heavy headings, generous empty space, the accent on the one thing that matters per slide (a number, a word, one shape), never several accent colors competing. Do not add decorative gradients or drop shadows to text. Write speaker notes for every slide with set_notes (what to say, the number to stress); the presenter sees them in presenter view. MAKE IT OUTSTANDING: unless the user wants a plain deck, finish every presentation with all three of these. (1) Shape the journey: arrange_slides with a layout that fits the story (orbits or a tree for a hub and its topics, spiral or sunflower for growth, staircase for progress, zoom-tunnel for drilling down, journey or wave for a story, carousel for a sleek linear deck: slides glide side by side over a parallax backdrop, the best match for an imported PowerPoint that should stay linear) instead of a flat row. The carousel template starts there directly. (2) Vary the camera: set_transitions (swoop, spin, punch and fade next to smooth; e.g. styles ["smooth", "swoop", "punch"] cycles them), with smooth for zooming out to an overview. (3) Animate inside the slides: auto_animate gives every slide a polished entrance cascade (titles focus, text rises, icons pop, numbers count up), then animate the key moments: spotlight or highlight on the one number or phrase that matters, count_up on metrics, words or typewriter on a quote, on-click rise to reveal points as the speaker talks, fade_out / fly_out to clear a slide before its punchline. Use at most one or two emphasis effects per slide.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| catalogA | Lists the presentation templates, slide layouts (with the text fields and icon slots each one has), color themes and the house style (the default look). Call this first. |
| search_iconsA | Searches the ~1,500 bundled Phosphor icon names (e.g. 'rocket', 'chart', 'users'). |
| create_presentationB | Creates a new GlideDeck project file from a template (default 'blank') and returns its slides with every element id and placeholder text. The file is a regular GlideDeck project the user can open and edit later. |
| get_presentationA | Returns the title, theme and slides in show order, with the id, name and current text of every text element, icon and image on each slide. |
| add_slideA | Adds a slide from a layout (see |
| update_elementsC | Changes elements by id: |
| add_textC | Adds a themed text box to a slide. Slide coordinates are 1600 × 900 units with (0, 0) at the center. |
| add_imageA | Copies an image or SVG file into the project's assets/ folder and places it on a slide (slide units: 1600 × 900, origin at the center). |
| add_web_videoB | Places a YouTube, Vimeo or Loom video (or a direct link to a video file) on a slide, with its title and poster image. It plays in GlideDeck and in the export_html web page (in the site's own player). Slide units: 1600 × 900, origin at the center. |
| set_themeA | Restyles the whole presentation with a theme from |
| remove_slideA | Removes a slide from the show; its frame and content are deleted unless keep_content is true or another step uses the same frame. |
| edit_presentationA | Applies a batch of low-level GlideDeck operations atomically (all or nothing). Ops: add_element {element}, remove_element {id}, set_transform {id, x?, y?, scale?, rotation?}, set_kind {id, kind}, set_name {id, name}, set_opacity {id, opacity}, reorder {id, index?}, set_title {title}, set_background {color}, add_step {frame, index?}, remove_step {index}, move_step {from, to}. Each op is an object with an "op" field, e.g. {"op":"set_transform","id":"text-1","y":120}. Coordinates here are world units. |
| render_slideA | Renders a slide (1-based step; 0 = the whole canvas) to a PNG and returns it, so you can check layout, overflow and contrast. Optionally also saves it. |
| export_pptxB | Exports the presentation to .pptx: one slide per step, with Morph transitions. Defaults to the project's name with .pptx. |
| export_htmlA | Exports the presentation to a single self-contained .html file that plays the show in any browser exactly like the app: the same camera moves, transitions, builds, parallax and effects, with text as vector outlines (no fonts needed) and images embedded. Videos are copied to a |
| list_fontsA | Lists the font families available for text: the fonts installed on this computer plus, when |
| add_fontA | Copies a .ttf/.otf/.ttc/.otc font file into the project's assets/ folder so it travels with the presentation, and returns its family names for |
| import_pptxA | Converts a .pptx into a GlideDeck project: each slide becomes a frame with its text (with formatting), shapes, pictures, background and speaker notes, in slide order. Tables, charts and SmartArt are listed as skipped. Returns the slides like get_presentation. |
| arrange_slidesA | Moves every slide on the path into a new layout and path (each slide's content moves with it; the order is kept). Great after import_pptx, which arrives as a plain grid. Layouts: carousel (slides side by side gliding over a parallax backdrop), spiral, orbits, sunflower, ring, honeycomb, journey, wave, staircase, tree, zoom-tunnel, snake, grid. |
| animateA | Adds in-slide animations (builds) to objects, played in order during the show: each |
| auto_animateA | Gives slides a polished entrance cascade in reading order that plays as the camera arrives: titles focus, text rises, numbers count up, icons pop, pictures zoom. Replaces those slides' animations. Then add key-moment emphasis with |
| set_transitionsA | Sets how the camera travels into slides: smooth (zoom out, then in), direct, swoop (sideways arc with a roll), spin (barrel roll), punch (overshoot and settle), fade (dip through the background) or cut. |
| set_notesB | Sets the speaker notes of slides (Markdown: # heading, - bullet, bold). The presenter sees them in presenter view, next to the live slide; the audience doesn't. |
| clear_animationsB | Removes the in-slide animations of the given slides (default: all). |
| export_pdfB | Exports the presentation to PDF: one page per slide on the path, rendered exactly as in the show. Defaults to the project's name with .pdf. |
| save_asB | Saves the project under a new name or folder (media files are copied along), e.g. to keep a version the user will edit later in GlideDeck. |
| open_in_editorA | Opens the project in the GlideDeck editor on the user's computer so they can edit and present it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Most tools target a clearly distinct resource or lifecycle stage (add_slide vs add_text vs add_image vs set_transitions), and the descriptions call out the intended split. The main ambiguity is `edit_presentation`, a low-level batch escape hatch that overlaps with update_elements, add_slide/remove_slide and set_theme, plus the adjacent pair `animate` / `auto_animate`, which the descriptions distinguish but an agent could still confuse.
The dominant pattern is a consistent snake_case verb_noun scheme (get_presentation, create_presentation, add_slide, remove_slide, export_pdf, set_notes). A few outliers break it: bare nouns (`catalog`), verb-only (`animate`), and suffixed forms (`auto_animate`, `save_as`, `open_in_editor`), but these remain readable and non-conflicting.
27 tools is heavy and sits at the top edge of what the domain needs, spread across authoring, styling, animation, import/export and file management. Nearly every tool earns its place, but the surface could be tightened (e.g. folding add_web_video/add_image/add_font into a generic asset tool, or dropping edit_presentation).
Coverage is broad: create/open/save, slide and element authoring, fonts, icons, images, video, themes, animation, transitions, notes, render preview, and export to HTML, PPTX and PDF plus PPTX import. Minor gaps remain — no dedicated delete-element or reorder-slide tool (only reachable through edit_presentation), and no duplicate-slide operation — but these are workable.