Skip to main content
Glama
alicenjr

Dynamic Reincarnation Story

by alicenjr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

reset_story

Clear all story progress and choices to restart the interactive reincarnation narrative from the beginning.

Instructions

Reset the story completely

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:352-357 (handler)
    The handler function for the 'reset_story' tool. It deletes the user's story state from the global dictionary and returns a confirmation message. Registered via @mcp.tool() decorator.
    @mcp.tool()
def reset_story(user_id: str) -> str:
    """Reset the story completely"""
    if user_id in story_states:
        del story_states[user_id]
    return "Story has been reset. Type 'Arise' to begin anew."

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden. 'Reset the story completely' suggests a destructive mutation, but it lacks details on permissions, reversibility, side effects, or what 'completely' means (e.g., data deletion, state clearing). This is inadequate for a mutation tool with zero annotation coverage.

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 is appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given a mutation tool with no annotations, 0% schema coverage, and an output schema (which might help), the description is incomplete. It fails to explain the tool's behavior, parameter meaning, or usage context, making it insufficient for effective agent invocation.

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. It provides no information about the 'user_id' parameter, such as its purpose, format, or how it relates to resetting the story. This leaves the single required parameter undocumented.

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 'Reset the story completely' specifies the verb 'reset' and the resource 'story', but lacks specificity about what 'story' refers to or what 'completely' entails. It distinguishes from siblings like 'get_story_status' or 'start_story' by implying a destructive reset, but the purpose remains somewhat vague without context.

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 guidance is provided on when to use this tool versus alternatives like 'start_story' or 'handle_user_message'. The description implies a reset action but does not specify prerequisites, timing, or exclusions, leaving usage unclear.

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