Presentation Agent MCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_style_profileD | 获取内置风格配置 |
| create_storylineC | 根据主题、受众、研究摘要生成故事线 |
| create_deckB | 根据主题或 storyline 创建 Deck JSON |
| get_deckB | 读取 Deck JSON |
| review_deckC | 审查 PPT 内容结构 |
| update_slideC | 增量修改单页 |
| export_pptxC | 导出 PPTX |
| export_pdfD | 导出 PDF |
| auto_fix_deckC | Auto-fix review issues in a 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 9 tools
Most tools have clearly distinct purposes: creation, retrieval, review, fixing, export, and styling. The only potential confusion is between auto_fix_deck and review_deck, but they are differentiated as 'review' checks while 'fix' applies changes.
Tools mostly follow a verb_noun pattern with underscores, but 'create_style_profile' is misleading because its description indicates it retrieves built-in styles rather than creating a new profile. This inconsistency reduces clarity.
With 9 tools, the server covers the essential operations for presentation creation from storyline to export without being overly numerous. The count feels well-scoped for its purpose.
The tool set covers core workflows (create storyline, create deck, review, fix, update slides, export) but lacks common operations like deleting a deck, adding or removing slides, or listing existing decks. These gaps could hinder full lifecycle management.