Skip to main content
Glama
Sign In
Dynamic Reincarnation Story

Dynamic Reincarnation Story

by alicenjr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_story

Programmatically initiate personalized reincarnation storytelling by providing a user ID to generate dynamic narrative paths based on character choices.

Instructions

Alternative way to start the story programmatically

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "start_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:202-216 (handler)
    The main handler function for the 'start_story' tool. It initializes the user's story state upon invocation and returns the initial reincarnation prompt.
    @mcp.tool()
def start_story(user_id: str) -> str:
    """Alternative way to start the story programmatically"""
    state = get_user_state(user_id)
    state.update({
        "current_path": None,
        "story_step": 0,
        "choices_made": [],
        "user_answers": {},
        "last_narrative": "",
        "current_context": "Beginning: User has died and is offered reincarnation",
        "story_started": True
    })
    
    return str(arise_trigger_response()) + "\n\n" + str(initial_reincarnation_offer())
  • main.py:202-202 (registration)
    The @mcp.tool() decorator registers the start_story function as an MCP tool.
    @mcp.tool()

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
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 'programmatically' but doesn't explain what the tool does beyond starting a story, such as whether it initializes data, requires authentication, or has side effects. This leaves significant gaps in understanding the tool's behavior.

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 with no wasted words, making it appropriately sized. However, it's front-loaded with minimal information, which could be improved by adding more context without sacrificing brevity.

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 has an output schema, the description doesn't need to explain return values, but it lacks details on behavior and usage. With no annotations and low schema coverage, the description is incomplete for a tool that likely involves story initialization, leaving gaps in understanding its full context.

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

Parameters3/5

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

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It doesn't add any meaning about the 'user_id' parameter, such as its role or format. However, with only one parameter, the baseline is 4, but the lack of any parameter explanation reduces it to 3, as the schema alone is insufficient.

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

Purpose2/5

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

The description states it's an 'alternative way to start the story programmatically,' which provides a vague purpose (starting a story) but lacks specificity about what 'starting' entails. It doesn't clearly distinguish from siblings like 'generate_path_introduction' or 'reset_story,' making it tautological by restating the tool name without concrete action details.

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 on when to use this tool versus alternatives is provided. The term 'alternative way' implies there might be other methods, but it doesn't specify what those are or under what conditions this tool is preferred, leaving usage unclear.

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

Deploy Server

Other Tools