Alai
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| api-key | No | API key from getalai.com used in the headers for authentication. | |
| Authorization | No | Bearer token for authentication (e.g., Bearer sk_your_key). |
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Verify the configured Alai credentials and return account identity details. Use this first when you need to confirm authentication before creating or exporting presentations. |
| generate_presentationA | Create a new presentation from raw text or markdown. Use this to turn notes, outlines, meeting summaries, or draft content into an Alai deck before polling get_generation_status. |
| get_generation_statusA | Check the status of an asynchronous presentation generation job. Use this after generate_presentation until the status reaches completed or failed. |
| get_themesA | List themes available to the authenticated account. Call this before generate_presentation when you need valid theme_id values. |
| get_vibesA | List available vibe identifiers that control the visual style of generated decks. Use this before setting vibe_id on generate_presentation or create_slide. |
| get_presentationsA | List presentations owned by the authenticated user. Use this when you need to pick an existing presentation_id before editing, exporting, or deleting. |
| create_slideA | Add a new slide to an existing presentation. Use this for targeted edits after a deck already exists, including classic content slides or more creative visually led slides. |
| delete_slideA | Remove a slide from a presentation permanently. Use this only when you know the exact slide identifier to delete. |
| export_presentationA | Export a finished presentation to PDF, PowerPoint, or a shareable link. Use this after generation or editing when you need a deliverable artifact. |
| generate_transcriptsA | Generate speaker notes or transcripts for slides in an existing presentation. Use this when the deck visuals are ready and you need talking points for delivery. |
| delete_presentationA | Delete a presentation permanently. Use this destructive action only when the caller explicitly intends to remove the deck. |
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 11 tools
Each tool targets a distinct action and resource, such as creating, deleting, exporting, or listing. No two tools have overlapping purposes, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_slide, delete_presentation, get_themes). This predictability aids agent understanding.
With 11 tools covering creation, deletion, export, status checking, listing, and authentication, the count is well-scoped for a presentation generation service.
The set lacks update operations (e.g., update_slide, update_presentation) and retrieval of a single presentation's details (e.g., get_slides). This could force agents to work around gaps, though core create/delete/export flows exist.