Skip to main content
Glama
septapod

Emoji Storyteller MCP Server

by septapod

tell_themed_story

Generate themed stories using only emojis for adventure, romance, horror, space, food, or party narratives.

Instructions

Tells a themed emoji story. Choose your adventure! πŸ—ΊοΈβœ¨

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
themeYesStory theme: 'adventure', 'romance', 'horror', 'space', 'food', or 'party'

Implementation Reference

  • Handler logic for tell_themed_story tool: extracts theme from input, generates story using generateThemedStory, and returns formatted output.
    if (toolName === "tell_themed_story") {
      const theme = toolInput.theme || "random";
      const story = generateThemedStory(theme);
      return `🎭 ${theme.toUpperCase()} STORY 🎭\n\n${story}`;
    }
  • Input schema for tell_themed_story, defining the required 'theme' string parameter with allowed enum values.
    inputSchema: {
      type: "object",
      properties: {
        theme: {
          type: "string",
          description:
            "Story theme: 'adventure', 'romance', 'horror', 'space', 'food', or 'party'",
          enum: ["adventure", "romance", "horror", "space", "food", "party"],
        },
      },
      required: ["theme"],
    },
  • index.js:121-137 (registration)
    Registration of the tell_themed_story tool in the TOOLS array, including name, description, and input schema.
    {
      name: "tell_themed_story",
      description:
        "Tells a themed emoji story. Choose your adventure! πŸ—ΊοΈβœ¨",
      inputSchema: {
        type: "object",
        properties: {
          theme: {
            type: "string",
            description:
              "Story theme: 'adventure', 'romance', 'horror', 'space', 'food', or 'party'",
            enum: ["adventure", "romance", "horror", "space", "food", "party"],
          },
        },
        required: ["theme"],
      },
    },
  • Helper function that generates predefined emoji stories for specific themes or falls back to random chaos.
    function generateThemedStory(theme) {
      const themeMap = {
        adventure: () => {
          return `πŸ—ΊοΈ πŸ§— πŸ”οΈ\n⚑ πŸ‰ πŸ’ͺ\nπŸ† πŸ’Ž ✨\nπŸŽ‰ πŸ₯³ 🎊`;
        },
        romance: () => {
          return `πŸ’• πŸ’‘ πŸ’\n🌹 😍 πŸ’«\nπŸ’” πŸ₯Ί 😒\nπŸ’•πŸ’•πŸ’•`;
        },
        horror: () => {
          return `🏚️ πŸ‘» 😱\nπŸ”ͺ πŸ’€ ☠️\n😲 πŸƒ πŸ’¨\nπŸŒ™ 😡 πŸ’₯`;
        },
        space: () => {
          return `πŸš€ 🌌 πŸ‘½\nπŸͺ ⭐ 🌠\nπŸ›Έ πŸ”­ πŸ’«\n🌍 πŸ’₯ πŸŽ†`;
        },
        food: () => {
          return `πŸ• πŸ” 🍟\nπŸ˜‹ 🀀 😍\n🍽️ πŸ”₯ πŸ’¨\nπŸ’€ 😱 πŸš€`;
        },
        party: () => {
          return `πŸŽ‰ 🎊 πŸ₯³\nπŸ’ƒ πŸ•Ί 🎡\n🍾 🍻 πŸŽͺ\n😡 πŸ’« ✨`;
        },
      };
    
      return themeMap[theme]
        ? themeMap[theme]()
        : `Random chaos incoming...\n${generateEmojiStory("random", 7)}`;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'themed emoji story' and 'Choose your adventure', but doesn't disclose behavioral traits such as output format (e.g., text length, emoji usage patterns), interactivity details, or any constraints like rate limits or permissions. This leaves significant gaps for a tool with no structured annotations.

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 appropriately sized and front-loaded: the first sentence states the core purpose, and the second adds engaging context without waste. Every sentence earns its place, making it efficient and clear.

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, 100% schema coverage, no output schema), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral aspects (e.g., output format, interactivity) that would be helpful since no annotations or output schema exist. It meets the minimum for this context but has clear gaps.

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?

Schema description coverage is 100%, with the 'theme' parameter fully documented in the schema (including enum values). The description adds no additional parameter semantics beyond what the schema provides, such as explaining how the theme influences the story. Baseline 3 is appropriate since the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Tells a themed emoji story' with the specific verb 'tells' and resource 'story', and it distinguishes from siblings by specifying 'themed' (vs. 'madness' or 'random'). However, it doesn't explicitly differentiate from 'tell_emoji_madness' or 'tell_random_story' in the description text, keeping it from a perfect score.

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

Usage Guidelines3/5

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

The description implies usage with 'Choose your adventure! πŸ—ΊοΈβœ¨', suggesting an interactive or selection context, but it doesn't explicitly state when to use this tool versus the siblings 'tell_emoji_madness' or 'tell_random_story'. No alternatives or exclusions are mentioned, leaving guidance incomplete.

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/septapod/mcp-emoji-stories'

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