showntell
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOWNTELL_DATA | No | Walkthroughs, audio cache, models, lockfile and log | ~/.local/share/showntell |
| SHOWNTELL_HOST | No | Interface; anything else requires an access token, which is generated and added to links | 127.0.0.1 |
| SHOWNTELL_PORT | No | Daemon port; the next free one is used if taken | 4747 |
| SHOWNTELL_VOICE | No | Default voice; any English Kokoro voice, such as am_michael or bf_emma | af_heart |
| SHOWNTELL_SPEECH | No | Speech backend: mlx on Apple silicon, onnx elsewhere, or fake for tests | auto |
| SHOWNTELL_THREADS | No | CPU threads for ONNX speech | up to 6 |
| SHOWNTELL_ONNX_MODEL | No | ONNX variant; model (fp32) can be faster on CPUs without AVX2 | model_quantized |
| SHOWNTELL_PUBLIC_URL | No | Base URL for links when viewing from another device, such as a Tailscale name; links then carry an access token |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_walkthroughA | Create a narrated walkthrough. Pass its opening in |
| add_slidesA | Append slides to a walkthrough, written in Markdown. Calls:
Format:
Inline code may set start=10.
|
| revise_slideA | Replace one slide, found by its id, with new Markdown. Only narration whose text changed is voiced again; the rest keeps its audio. Omit the heading to keep the slide's title, classes and attributes. Use it for a slide a reply reported as broken, or to rework a finished walkthrough: find its handle with list_walkthroughs and read its Markdown from the resource showntell://walkthroughs/{id}. |
| finish_walkthroughA | Close the walkthrough after its last slide. Records the end questions and returns a summary with any remaining problems. Then tell the user it is finished and give the link. |
| list_walkthroughsA | List recent walkthroughs with their handles, titles and links. Use it to find the handle of a walkthrough to revise later, including one from an earlier session. Its Markdown source is the resource showntell://walkthroughs/{id}, where id is the part of the handle before the dot. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| diff | Narrated walkthrough of a commit range, a branch or the working tree. |
| file | Narrated walkthrough of one source file. |
| topic | Narrated walkthrough of a concept, algorithm, design or piece of maths. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| walkthroughs | Recent walkthroughs with titles, links and handles |
TDQS
Scored across 5 tools
Each tool maps to a distinct lifecycle step (start, add, revise, list, finish), so selection is mostly clear. The one blur is that add_slides can optionally carry the opening that start_walkthrough normally owns, creating a documented overlap between the two.
All names are snake_case verb_noun (start_walkthrough, add_slides, revise_slide, list_walkthroughs, finish_walkthrough), which is highly predictable. Minor deviation: some nouns are plural (slides, walkthroughs) while others are singular (slide, walkthrough).
Five tools cleanly cover the create/append/edit/list/close workflow for narrated walkthroughs. Each earns its place with no redundant surface.
The lifecycle is well covered from creation through finishing and later revision (via list_walkthroughs plus revise_slide). A delete/remove walkthrough operation is absent, but core authoring flows have no dead ends.