Skip to main content
Glama
alicenjr

Dynamic Reincarnation Story

by alicenjr

get_story_status

Retrieve the current status and state of your interactive reincarnation story, including narrative progress and character development based on your choices.

Instructions

Get current story status and state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:340-350 (handler)
    The core handler function that implements the logic for the 'get_story_status' tool. It retrieves the user's story state using get_user_state and returns it as a formatted JSON string.
    def get_story_status(user_id: str) -> str:
        """Get current story status and state"""
        state = get_user_state(user_id)
        return json.dumps({
            "story_started": state["story_started"],
            "current_path": state["current_path"],
            "story_step": state["story_step"],
            "choices_made": state["choices_made"],
            "current_context": state["current_context"],
            "has_answers": len(state["user_answers"]) > 0
        }, indent=2)
  • main.py:339-339 (registration)
    The @mcp.tool() decorator registers the get_story_status function as an MCP tool, making it available for invocation.
    @mcp.tool()
  • main.py:12-24 (helper)
    Helper function used by get_story_status to retrieve or initialize the user's persistent story state from the global story_states dictionary.
    def get_user_state(user_id: str) -> Dict[str, Any]:
        """Get or create user story state"""
        if user_id not in story_states:
            story_states[user_id] = {
                "current_path": None,
                "story_step": 0,
                "choices_made": [],
                "user_answers": {},
                "last_narrative": "",
                "current_context": "",
                "story_started": False
            }
        return story_states[user_id]
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 states 'Get current story status and state', implying a read-only operation, but doesn't specify whether this requires authentication, what happens if no story exists, or the format of the returned status/state. This leaves significant gaps in understanding the tool's behavior beyond basic intent.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action ('Get current story status and state'), making it easy to parse quickly. Every word contributes directly to the tool's purpose.

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 low complexity (1 parameter, no nested objects) and the presence of an output schema (which should document return values), the description is minimally adequate. However, it lacks context about prerequisites, error conditions, or how it fits with siblings, leaving gaps that could hinder effective use despite the output schema.

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?

The input schema has 1 parameter (user_id) with 0% description coverage, meaning the schema provides no semantic context. The description adds no information about parameters, failing to explain what 'user_id' represents (e.g., a specific user identifier) or how it relates to retrieving story status. This doesn't compensate for the low schema coverage.

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 'Get current story status and state' clearly indicates a retrieval operation ('Get') on a specific resource ('story status and state'), which is better than a tautology. However, it doesn't distinguish this tool from potential siblings like 'reset_story' or 'start_story' in terms of scope or granularity, leaving the purpose somewhat vague.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active story), exclusions (e.g., not for modifying status), or comparisons to siblings like 'reset_story' or 'record_answers_and_choose_path', leaving the agent to infer usage from context alone.

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