Skip to main content
Glama
alicenjr

Dynamic Reincarnation Story

by alicenjr

record_answers_and_choose_path

Store user responses to soul-searching questions and select their personalized reincarnation story path in an interactive narrative experience.

Instructions

Record user's answers and choose their reincarnation path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
answersYes
path_choiceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:228-266 (handler)
    This is the main handler function for the 'record_answers_and_choose_path' tool. It is decorated with @mcp.tool(), which registers it in the FastMCP server. The function records the user's three answers into the story state, maps the path_choice (1-3) to a path ('revenge', 'bilbo', or 'luffy'), updates the state, and returns a narrative confirmation message.
    @mcp.tool()
    def record_answers_and_choose_path(user_id: str, answers: List[str], path_choice: int) -> str:
        """Record user's answers and choose their reincarnation path"""
        state = get_user_state(user_id)
        
        if not state["story_started"]:
            return "Please start the story first by typing 'Arise'."
        
        if len(answers) != 3:
            return "Please provide exactly three answers, one for each question."
        
        # Record answers
        state["user_answers"] = {
            "betrayal_wound": answers[0],
            "adventure_desire": answers[1],
            "freedom_calling": answers[2]
        }
        
        # Choose path
        paths = {1: "revenge", 2: "bilbo", 3: "luffy"}
        if path_choice not in paths:
            return "Invalid path choice. Please choose 1, 2, or 3."
        
        state["current_path"] = paths[path_choice]
        state["story_step"] = 0
        state["current_context"] = f"Beginning {state['current_path']} path after reincarnation"
        
        return f"""
    Your answers have been recorded and your path chosen. 
    
    **Path Selected:** {paths[path_choice].title()}
    
    The entity now understands your soul's true desires and will transport you to your new life. 
    
    "I see... your soul cries out for {['vengeance', 'adventure', 'freedom'][path_choice-1]}. Very well. Prepare yourself for rebirth into the {paths[path_choice]} path."
    
    The world dissolves around you as the reincarnation process begins...
    """
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions recording and choosing actions, which imply mutation or state changes, but fails to detail permissions, side effects, rate limits, or response behavior. This is inadequate for a tool with potential write operations and no structured safety hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action. It avoids unnecessary words, though it could be more informative. The structure is straightforward, but brevity comes at the cost of clarity and completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, no annotations, but with an output schema), the description is minimally adequate. The output schema may cover return values, reducing the need for that in the description, but key aspects like behavioral traits and parameter details are lacking, making it incomplete for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for three undocumented parameters. It only vaguely references 'answers' and 'path_choice' without explaining their formats, constraints, or relationships (e.g., what answers are recorded, what path_choice values mean). This adds minimal meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as recording user answers and choosing a reincarnation path, which is clear but somewhat vague. It specifies the verb 'record' and 'choose' with the resources 'answers' and 'path', but lacks detail on what 'reincarnation path' means or how it relates to siblings like 'generate_path_introduction' or 'get_story_status', limiting differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is provided on when to use this tool versus alternatives. The description implies usage in a story or reincarnation context but does not specify prerequisites, exclusions, or comparisons to siblings such as 'process_user_input' or 'handle_user_message', leaving the agent with minimal direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alicenjr/Dynamic-Reincarnation-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server