Dynamic Reincarnation Story
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| handle_user_messageC | Main entry point - handle any user message and route accordingly |
| start_storyC | Alternative way to start the story programmatically |
| ask_guidance_questionsC | Present the three guidance questions to the user |
| record_answers_and_choose_pathC | Record user's answers and choose their reincarnation path |
| generate_path_introductionC | Generate the introduction narrative for the chosen path |
| process_user_inputC | Process user input and generate narrative response with options |
| get_story_statusC | Get current story status and state |
| reset_storyC | Reset the story completely |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| initial_reincarnation_offer | Initial story setup - death and reincarnation offer |
| three_guidance_questions | Three questions to guide the reincarnation choice |
| arise_trigger_response | Response when user types 'Arise' to start the story |
| generate_narrative_prompt | Generate a narrative response based on user input and story context |
| generate_options_prompt | Generate three story progression options based on current narrative |
| path_introduction_prompt | Generate an introduction narrative when a path is chosen |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
The tools have some overlapping purposes that could cause confusion, particularly between handle_user_message and process_user_input which both seem to handle user input processing. However, descriptions help clarify distinctions like start_story vs ask_guidance_questions for different initiation methods.
Most tools follow a consistent verb_noun pattern (e.g., ask_guidance_questions, generate_path_introduction, get_story_status) with clear action-object relationships. The only minor deviation is handle_user_message which uses 'handle' instead of a more specific verb, but overall naming is predictable and readable.
With 8 tools, this is well-scoped for an interactive story system. Each tool appears to serve a distinct phase in the story lifecycle (initialization, progression, status tracking, reset), and none seem redundant or unnecessary for the domain.
The toolset covers the core interactive story workflow well: starting, progressing through user input, tracking status, and resetting. A minor gap might be the lack of tools for modifying story parameters or saving/loading states, but the basic narrative flow is fully supported.