Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WORKSPACE_ROOTNoEnvironment variable specifying the workspace root. Used as a fallback after CHATPPT_WORKSPACE_ROOT and before process.cwd().
CHATPPT_WORKSPACE_ROOTNoEnvironment variable specifying the workspace root. Resolved after the --workspace/-w command line argument and before WORKSPACE_ROOT. Falls back to process.cwd() if unset.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
deck_importC

Import an existing PowerPoint deck into the managed workspace and initialize its registry metadata.

deck_createA

Create a new blank PowerPoint presentation deck and initialize its metadata in the managed workspace.

deck_listA

List all managed PowerPoint decks in the workspace.

deck_readB

Read metadata, slide list, and slide collections for a specific deck.

deck_updateC

Update metadata or title of an existing presentation deck.

deck_deleteA

Permanently delete a presentation deck and its underlying PowerPoint file.

deck_validateA

Validate presentation deck integrity, checking PPTX file synchronization, collection slide references, and element geometry.

slide_createB

Create one or multiple new slides in a presentation deck. Pass an array of slide definitions for vectorized batch creation.

slide_listB

List all slides in a presentation deck in presentation order.

slide_readA

Read metadata, elements, and speaker notes for a specific slide.

slide_renderA

Render a slide to a PNG image preview for visual feedback.

slide_updateC

Update metadata, title, or speaker notes of one or more slides in batch.

slide_deleteA

Permanently delete one or more slides from the presentation and registry, and clean up collection references.

slide_moveA

Reorder slides in a presentation deck, either by providing a complete slideOrder array or moving a single slideId to a target position.

slide_duplicateB

Duplicate an existing slide in a presentation deck, generating new stable IDs for the slide and all duplicated elements.

slide_collection_createC

Create a named ordered collection/group of existing slides within a presentation deck.

slide_collection_listC

List all slide collections in a presentation deck.

slide_collection_readB

Read details and slide ID membership of a specific slide collection.

slide_collection_updateA

Rename a slide collection, update its description, or replace its ordered slide membership.

slide_collection_deleteA

Delete a slide collection without deleting its referenced slides.

element_createB

Create one or multiple elements (text boxes, shapes, lines, tables, charts, or images) on a slide in a single batch operation.

element_listA

List all visual elements on a slide in z-index order.

element_readA

Read details and formatting properties of a single element on a slide.

element_updateB

Update positioning, sizing, text, fill, typography, stroke, or alignment for one or multiple elements on a slide in batch.

element_deleteB

Permanently delete one or more elements from a slide in batch.

element_reorderB

Reorder an element's z-index on a slide (bringToFront, sendToBack, bringForward, sendBackward).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 26 tools

Disambiguation4/5

Tools are clearly grouped by resource (deck, slide, slide_collection, element) with distinct CRUD/list verbs, so most selections are straightforward. Minor overlap exists because deck_read returns slide lists and collections, and slide_collection_list is close to slide_list, but descriptions resolve this.

Naming Consistency5/5

All tools follow a consistent snake_case resource/action pattern (e.g., deck_create, slide_update, element_reorder). Multi-word resources like slide_collection are handled uniformly across create/read/update/delete/list.

Tool Count3/5

At 26 tools the surface is heavy, though the multi-resource domain of decks, slides, collections, and elements justifies many operations. Batch operations help, but there is still some consolidation opportunity, placing it at the borderline.

Completeness4/5

Deck, slide, collection, and element lifecycles are well covered, including import, validation, duplication, reordering, rendering, and batch updates. Minor gaps include no deck export/download and no obvious cross-deck copy or slide search.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues