merlin-slides-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_deckA | Turn a plain-text outline into a complete, self-contained HTML presentation (arrow-key navigation built in). Outline format: '# Slide title' starts a slide; each following line is a bullet; indent two spaces for sub-points. Returns the full HTML document as text — save it as .html and it works anywhere, offline. |
| check_outlineA | Validate a Merlin Slides outline: counts slides/bullets and flags empty slides or very long bullets (>160 chars) before you build. |
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 2 tools
Each tool targets a clearly distinct operation: build_deck produces HTML output, while check_outline performs validation only. There is a natural pre-flight/build relationship but no overlap in behavior, so an agent can easily choose the right tool.
Both names use snake_case with a verb_noun structure (build_deck, check_outline), which is consistent in style. The verbs differ in category (build vs check) but each accurately describes its action, so this is a minor, acceptable deviation.
Only two tools exist, which is thin for a deck-building domain; content authoring, theming, and export are unaddressed. The pair is logically coherent but borderline minimal, leaving an agent with limited leverage.
The surface covers the core validate-then-build flow, which is a complete minimal lifecycle. However, there are notable gaps: no way to preview slides, customize styling, or edit an existing deck, so agents may hit dead ends for non-trivial presentations.