Teleprompter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMPT_STORAGE_PATH | Yes | The absolute path where you want prompts stored |
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 |
|---|---|
| createPromptA | Create a new Teleprompter prompt. Wrap template variables in double curly braces. For example, "Hello, {{name}}!" |
| usePromptA | If the user has sent a message containing a prompt tag, use the this tool to fetch the prompt, and follow its instructions. For example, if the user sends ">> new-journal-entry", this tool will fetch the prompt with the ID "new-journal-entry", so you can use it to generate a new journal entry. Template variables may be included in the template, and are marked with double curly braces. For example, "Hello, {{name}}!". Based on your current session with the end user, fill in values for these variables. If a value cannot be determined, ask the user for it, then follow the instructions in the prompt. |
| searchPromptsA | Fuzzy search the available Teleprompter prompts by text. Returns a list of matching prompt IDs and their content, so the user can discover prompts even if they do not know the exact tag or ID. |
| listPromptsA | List all available Teleprompter prompts. Returns a list of all prompt IDs and their content. |
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 4 tools
Mostly distinct purposes: createPrompt writes, usePrompt fetches and executes, searchPrompts and listPrompts both read but differ in scope (fuzzy search vs. full list). The descriptions clarify the distinction between search and list, so confusion is unlikely.
All tool names follow a verb + noun pattern with camelCase, but there is a minor inconsistency: createPrompt and usePrompt use singular 'Prompt' while searchPrompts and listPrompts use plural 'Prompts'. This is a minor deviation but still readable.
Four tools is well-scoped for a prompt management and usage server. Each tool serves a clear, necessary function (create, use, search, list) without redundancy or bloat.
The core create/read/use operations are covered, but update and delete are missing. This is a notable gap for managing a prompt library, as prompts cannot be edited or removed after creation, potentially causing stale or incorrect prompts to persist.