Skip to main content
Glama
Ripnrip

Quake Coding Arena MCP

by Ripnrip

random_enhanced_achievement

Trigger random achievement sounds from Quake 3 Arena to gamify coding milestones and provide audio feedback for development progress.

Instructions

🎲 Play a random achievement sound from a specific category. Useful for surprise celebrations or testing different achievement sounds. Returns the selected achievement name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo🎯 Filter achievements by category. Options: 'streak' (RAMPAGE, DOMINATING, etc.), 'quality' (EXCELLENT, PERFECT, etc.), 'multi' (WICKED SICK, HEADSHOT, etc.), 'game' (FIRST BLOOD, HUMILIATION, etc.), 'team' (PREPARE TO FIGHT, PLAY). If omitted, selects from all categories.
volumeNo🔊 Volume level for audio playback (0-100). Default is 80. Higher values increase audio volume.

Implementation Reference

  • Handler function that implements the core logic for the 'random_enhanced_achievement' tool: selects a random achievement by optional category filter, plays the sound, updates stats, and returns formatted response.
    async ({ category, volume }) => {
        const randomAchievement = EnhancedSoundOracle.getRandomAchievement(category);
    
        if (!randomAchievement) {
            return {
                content: [{
                    type: "text",
                    text: "❌ No achievements found for the specified category"
                }],
                success: false
            };
        }
    
        try {
            await EnhancedSoundOracle.playAchievementSound(randomAchievement, volume || 80, null, enhancedStats.voicePack);
            return {
                content: [{
                    type: "text",
                    text: `🎲 Random achievement: ${randomAchievement} played!`
                }],
                success: true,
                achievement: randomAchievement
            };
        } catch (error) {
            return {
                content: [{
                    type: "text",
                    text: `❌ Error playing ${randomAchievement}: ${error instanceof Error ? error.message : String(error)}`
                }],
                success: false
            };
        }
  • Zod input schema defining parameters for the tool: optional 'category' enum and 'volume' number with validation.
        category: z.enum(["streak", "quality", "multi", "game", "team"]).optional().describe("🎯 Filter achievements by category. Options: 'streak' (RAMPAGE, DOMINATING, etc.), 'quality' (EXCELLENT, PERFECT, etc.), 'multi' (WICKED SICK, HEADSHOT, etc.), 'game' (FIRST BLOOD, HUMILIATION, etc.), 'team' (PREPARE TO FIGHT, PLAY). If omitted, selects from all categories."),
        volume: z.number().min(0).max(100).default(80).describe("🔊 Volume level for audio playback (0-100). Default is 80. Higher values increase audio volume."),
    },
  • MCP server tool registration for 'random_enhanced_achievement' including full schema, annotations, and handler reference.
    server.registerTool(
        "random_enhanced_achievement",
        {
            description: "🎲 Play a random achievement sound from a specific category. Useful for surprise celebrations or testing different achievement sounds. Returns the selected achievement name.",
            inputSchema: {
                category: z.enum(["streak", "quality", "multi", "game", "team"]).optional().describe("🎯 Filter achievements by category. Options: 'streak' (RAMPAGE, DOMINATING, etc.), 'quality' (EXCELLENT, PERFECT, etc.), 'multi' (WICKED SICK, HEADSHOT, etc.), 'game' (FIRST BLOOD, HUMILIATION, etc.), 'team' (PREPARE TO FIGHT, PLAY). If omitted, selects from all categories."),
                volume: z.number().min(0).max(100).default(80).describe("🔊 Volume level for audio playback (0-100). Default is 80. Higher values increase audio volume."),
            },
            annotations: {
                title: "🎲 Random Achievement",
                readOnlyHint: false,
                destructiveHint: false,
                idempotentHint: false,
                openWorldHint: true
            }
        },
        async ({ category, volume }) => {
            const randomAchievement = EnhancedSoundOracle.getRandomAchievement(category);
    
            if (!randomAchievement) {
                return {
                    content: [{
                        type: "text",
                        text: "❌ No achievements found for the specified category"
                    }],
                    success: false
                };
            }
    
            try {
                await EnhancedSoundOracle.playAchievementSound(randomAchievement, volume || 80, null, enhancedStats.voicePack);
                return {
                    content: [{
                        type: "text",
                        text: `🎲 Random achievement: ${randomAchievement} played!`
                    }],
                    success: true,
                    achievement: randomAchievement
                };
            } catch (error) {
                return {
                    content: [{
                        type: "text",
                        text: `❌ Error playing ${randomAchievement}: ${error instanceof Error ? error.message : String(error)}`
                    }],
                    success: false
                };
            }
        }
    );
  • Handler method in standalone MCP server implementation that handles 'random_enhanced_achievement' by selecting random achievement and delegating to general sound play handler.
    async playRandomEnhancedAchievement(args) {
      const { category, volume = enhancedStats.volume } = args;
    
      const randomAchievement = EnhancedSoundOracle.getRandomAchievement(category);
    
      if (!randomAchievement) {
        throw new McpError(
          ErrorCode.InternalError,
          "🎲 No enhanced achievements available for the specified category!"
        );
      }
    
      return await this.handleEnhancedSoundPlay({
        achievement: randomAchievement,
        volume: volume
      });
    }
  • JSON schema for tool input in the ListTools response for 'random_enhanced_achievement'.
    inputSchema: {
      type: "object",
      properties: {
        category: {
          type: "string",
          description: "🎯 Filter by category (streak, quality, multi, game, team, powerup, custom)",
          enum: ["streak", "quality", "multi", "game", "team", "powerup", "custom"],
        },
        volume: {
          type: "number",
          description: "🔊 Enhanced volume level (0-100)",
          minimum: 0,
          maximum: 100,
          default: 80,
        },
      },
Behavior3/5

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

Annotations provide key behavioral hints (readOnlyHint=false, openWorldHint=true, etc.), covering safety and scope. The description adds context about audio playback and the random selection process, but does not disclose additional traits like rate limits, error handling, or side effects beyond what annotations imply. It does not contradict annotations, so a baseline score is appropriate given the 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 front-loaded with the core purpose in the first sentence, followed by usage context and return value. Every sentence earns its place by adding value (e.g., 'Useful for...' clarifies intent, 'Returns...' informs output). It is appropriately sized with no redundant or verbose language.

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

Completeness4/5

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

Given the tool's moderate complexity (2 parameters, no output schema), annotations cover behavioral aspects, and the description provides purpose, usage, and return info. However, it lacks details on error cases or audio playback specifics (e.g., format, duration), which could be helpful. Overall, it is mostly complete but has minor 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 detailed descriptions for both parameters (category with enum explanations and volume with range and default). The description does not add meaning beyond the schema, as it only mentions 'specific category' and 'audio playback' without extra details. Baseline 3 is correct since the schema fully documents parameters.

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

Purpose5/5

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

The description clearly states the specific action ('Play a random achievement sound') and resource ('from a specific category'), distinguishing it from siblings like 'list_enhanced_achievements' (which lists) or 'play_enhanced_quake_sound' (which plays specific sounds). It also mentions the return value ('Returns the selected achievement name'), making the purpose explicit and differentiated.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('Useful for surprise celebrations or testing different achievement sounds'), but does not explicitly state when not to use it or name alternatives among siblings (e.g., 'play_enhanced_quake_sound' for non-random sounds). This gives good guidance but lacks explicit exclusions or comparisons.

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/Ripnrip/Quake-Coding-Arena-MCP'

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