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.
This server publishes no instructions, or was last inspected before Glama recorded them.
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) and color themes. Call this first. |
| search_iconsA | Searches the ~1,500 bundled Phosphor icon names (e.g. 'rocket', 'chart', 'users'). |
| create_presentationA | 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_elementsA | 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). |
| 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. |
| 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 23 tools
Most tools target clearly distinct resources and actions (render_slide for previewing, export_pptx/pdf for file output, add_text vs add_slide, animate vs auto_animate). The main ambiguity is edit_presentation, a low-level batch tool whose ops (add_step, remove_step, set_transform) overlap conceptually with dedicated tools like add_slide, remove_slide, and update_elements, so an agent may be unsure which path to use.
Strong verb_noun pattern throughout (render_slide, add_slide, export_pptx, set_theme, clear_animations). A few deviations—catalog (bare noun), animate (verb with no object), and auto_animate—are minor but keep it from being perfectly uniform.
23 tools is on the heavier end but each maps to a real capability of a full presentation editor (creation, import/export, layout, animation, theming, notes). It is slightly large but well-scoped, with few tools that feel redundant.
Coverage is broad: create/import/open, add/remove slides, add text/images, edit elements, theming, transitions, animations, notes, save and multi-format export. Minor gaps exist (no dedicated element-delete or slide-duplicate outside the catch-all edit_presentation), but core lifecycles are covered.