Prompt Book Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_BOOKS | No | JSON string containing default prompt book configuration. Only used if config file doesn't exist. |
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_prompt_book_configC | Add a new prompt book configuration |
| copy_promptB | Copy a prompt from one book to another |
| remove_prompt_book_configC | Remove a prompt book configuration |
| activate_prompt_bookB | Set a prompt book as active |
| list_prompt_booksA | List all configured prompt books |
| rename_prompt_bookA | Rename a prompt book configuration |
| list_promptsB | List all prompts in the database |
| search_prompts_by_titleC | Search prompts by title |
| get_prompts_by_tagB | Get prompts by tag |
| get_prompts_by_typeB | Get prompts by type |
| read_promptA | Read the content of a specific prompt |
| list_all_typesA | List all unique prompt types in the database |
| list_all_tagsA | List all unique tags used in the database |
| create_prompt_databaseB | Create a new prompt database and add it to the configuration |
| add_promptB | Add a new prompt to the database |
| update_promptC | Update an existing prompt in the database |
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 16 tools
Each tool targets a distinct entity or action: prompt book configs, prompt databases, individual prompts, and metadata queries. The list/search/get operations are clearly separated by their parameters and descriptions, so there is little risk of selecting the wrong tool.
Most tools follow a consistent verb_noun pattern such as create_prompt_book_config, list_prompts, and rename_prompt_book. The main inconsistency is using both read_prompt and get_prompts_by_* for retrieval, but the overall naming remains predictable.
At 16 tools, the set is slightly above the ideal range, but the domain covers both book configuration management and prompt metadata retrieval. Each tool has a clear purpose, though the number is on the higher end for a single server.
The server covers prompt book lifecycle operations, database creation, and prompt add/update/read/query operations. However, there is no delete or remove prompt tool and no way to remove a prompt database, so lifecycle management is incomplete for the core prompt entity.