Skip to main content
Glama
septapod

Emoji Storyteller MCP Server

by septapod

tell_random_story

Generate unpredictable emoji stories with adjustable chaos levels for entertainment and creative inspiration.

Instructions

Tells a completely random and chaotic emoji story. Perfect for when you want pure chaos! 🎭✨

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chaos_levelNoHow chaotic the story should be (1-10). Default: 5

Implementation Reference

  • Executes the tell_random_story tool: extracts chaos_level (default 5), generates story using helper function, and returns formatted emoji story.
    if (toolName === "tell_random_story") {
      const chaosLevel = toolInput.chaos_level || 5;
      const story = generateEmojiStory("random", chaosLevel);
      return `🎬 EMOJI STORY (Chaos Level: ${chaosLevel}/10) 🎬\n\n${story}`;
    }
  • Defines the input schema for tell_random_story tool with optional chaos_level parameter.
    inputSchema: {
      type: "object",
      properties: {
        chaos_level: {
          type: "number",
          description: "How chaotic the story should be (1-10). Default: 5",
          minimum: 1,
          maximum: 10,
        },
      },
    },
  • index.js:105-120 (registration)
    Tool definition and registration in the TOOLS array used by ListToolsRequestHandler.
    {
      name: "tell_random_story",
      description:
        "Tells a completely random and chaotic emoji story. Perfect for when you want pure chaos! 🎭✨",
      inputSchema: {
        type: "object",
        properties: {
          chaos_level: {
            type: "number",
            description: "How chaotic the story should be (1-10). Default: 5",
            minimum: 1,
            maximum: 10,
          },
        },
      },
    },
  • Core helper function that generates the chaotic emoji story by building scenes from random emojis based on chaos level.
    function generateEmojiStory(theme = "random", chaosLevel = 5) {
      const scenes = [];
      const storyLength = chaosLevel + 3;
    
      // Act I - The Setup
      scenes.push(
        `Act I: ${getRandomEmojis("places", 1)} ${getRandomEmojis("animals", 2)}`
      );
      scenes.push(
        `${getRandomEmojis("emotions", 1)} ${getRandomEmojis("weather", 1)}`
      );
    
      // Act II - The Chaos
      for (let i = 0; i < storyLength; i++) {
        const sceneType = Math.random();
        if (sceneType < 0.3) {
          // Action scene
          scenes.push(
            `${getRandomEmojis("action", 2)} ${getRandomEmojis("objects", 1)} ${getRandomEmojis("action", 1)}`
          );
        } else if (sceneType < 0.6) {
          // Emotional scene
          scenes.push(
            `${getRandomEmojis("emotions", 2)} ${getRandomEmojis("magic", 1)}`
          );
        } else {
          // Complete randomness
          scenes.push(
            `${getRandomEmojis("silly", 1)} ${getRandomEmojis("food", 1)} ${getRandomEmojis("animals", 1)} ${getRandomEmojis("objects", 1)}`
          );
        }
      }
    
      // Act III - The Climax
      scenes.push(
        `⚡💥 ${getRandomEmojis("magic", 2)} 🎆 ${getRandomEmojis("animals", 1)} 💫`
      );
    
      // The Ending (always weird)
      scenes.push(`THE END... OR IS IT? 🎭✨🌀`);
    
      return scenes.join("\n");
    }
  • Utility helper to select random emojis from predefined categories, used in story generation.
    function getRandomEmojis(category, count = 1) {
      const emojis = EMOJIS[category];
      const result = [];
      for (let i = 0; i < count; i++) {
        result.push(emojis[Math.floor(Math.random() * emojis.length)]);
      }
      return result;
    }
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 the story is 'random and chaotic' and includes emojis, but doesn't describe key traits like output format, length, or any constraints beyond chaos level. This leaves gaps in understanding how the tool behaves, such as whether it returns text, emojis only, or structured data.

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, with two concise sentences that directly convey the tool's purpose and usage context. Every sentence earns its place by adding value, and there's no wasted verbiage, making it efficient and easy to parse.

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 output schema, no annotations), the description is somewhat complete but has gaps. It covers the purpose and hints at usage, but lacks details on behavioral traits and output, which are important for an agent to invoke it correctly. This makes it adequate but not fully comprehensive.

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 100% description coverage, fully documenting the 'chaos_level' parameter with its type, range, and default. The description adds no additional meaning beyond the schema, as it doesn't explain how chaos level affects the story (e.g., more emojis, randomness). This meets the baseline score of 3 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 with a specific verb ('Tells') and resource ('random and chaotic emoji story'), making it easy to understand what it does. However, it doesn't explicitly differentiate from its sibling tools (tell_emoji_madness, tell_themed_story), which would require mentioning how 'random and chaotic' contrasts with their themes or madness levels.

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 provides implied usage guidance by stating it's 'Perfect for when you want pure chaos!', which suggests a context for use. However, it lacks explicit when-to-use or when-not-to-use instructions, and doesn't mention alternatives like the sibling tools, leaving the agent to infer when this tool is preferred over others.

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