Skip to main content
Glama
Ripnrip

Quake Coding Arena MCP

by Ripnrip

set_voice_pack

Switch between male and female announcer voice packs to customize achievement sound feedback for coding milestones in your development environment.

Instructions

🎤 Switch between Male and Female announcer voice packs. This sets the default voice pack for all subsequent achievement sounds. Male pack includes 15 classic Quake 3 Arena sounds. Female pack includes 16 unique female announcer sounds. The setting persists for the session until changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voiceGenderYes🎤 Voice pack selection. Options: 'male' (Classic Quake 3 Arena male announcer with 15 sounds including EXCELLENT, PERFECT, IMPRESSIVE, DOUBLE KILL, TRIPLE KILL), 'female' (Female announcer with 16 sounds including HEADSHOT, MULTI KILL, KILLING SPREE, BOTTOM FEEDER, PLAY). Examples: 'male', 'female'

Implementation Reference

  • The core handler function for the 'set_voice_pack' tool. It updates the global enhancedStats.voicePack based on the input voiceGender ('male' or 'female'), retrieves the corresponding voice configuration from VOICE_PACKS, and returns a properly formatted MCP tool response including a text message and voice pack details.
    async ({ voiceGender }) => {
        enhancedStats.voicePack = voiceGender;
        const voiceConfig = VOICE_PACKS[voiceGender];
    
        return {
            content: [{
                type: "text",
                text: `🎤 Voice pack set to ${voiceConfig.displayName}!`
            }],
            currentVoicePack: voiceGender,
            voicePackInfo: voiceConfig
        };
    }
  • The tool specification including description, inputSchema using Zod for voiceGender enum validation, and annotations for UI hints.
    "set_voice_pack",
    {
        description: "🎤 Switch between Male and Female announcer voice packs. This sets the default voice pack for all subsequent achievement sounds. Male pack includes 15 classic Quake 3 Arena sounds. Female pack includes 16 unique female announcer sounds. The setting persists for the session until changed.",
        inputSchema: {
            voiceGender: z.enum(["male", "female"]).describe("🎤 Voice pack selection. Options: 'male' (Classic Quake 3 Arena male announcer with 15 sounds including EXCELLENT, PERFECT, IMPRESSIVE, DOUBLE KILL, TRIPLE KILL), 'female' (Female announcer with 16 sounds including HEADSHOT, MULTI KILL, KILLING SPREE, BOTTOM FEEDER, PLAY). Examples: 'male', 'female'"),
        },
        annotations: {
            title: "🎤 Set Voice Pack",
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: false,
            openWorldHint: false
        }
    },
  • The server.registerTool call that registers the 'set_voice_pack' tool with its spec and handler on the MCP server.
    // 🎤 Set Voice Pack
    server.registerTool(
        "set_voice_pack",
        {
            description: "🎤 Switch between Male and Female announcer voice packs. This sets the default voice pack for all subsequent achievement sounds. Male pack includes 15 classic Quake 3 Arena sounds. Female pack includes 16 unique female announcer sounds. The setting persists for the session until changed.",
            inputSchema: {
                voiceGender: z.enum(["male", "female"]).describe("🎤 Voice pack selection. Options: 'male' (Classic Quake 3 Arena male announcer with 15 sounds including EXCELLENT, PERFECT, IMPRESSIVE, DOUBLE KILL, TRIPLE KILL), 'female' (Female announcer with 16 sounds including HEADSHOT, MULTI KILL, KILLING SPREE, BOTTOM FEEDER, PLAY). Examples: 'male', 'female'"),
            },
            annotations: {
                title: "🎤 Set Voice Pack",
                readOnlyHint: false,
                destructiveHint: false,
                idempotentHint: false,
                openWorldHint: false
            }
        },
        async ({ voiceGender }) => {
            enhancedStats.voicePack = voiceGender;
            const voiceConfig = VOICE_PACKS[voiceGender];
    
            return {
                content: [{
                    type: "text",
                    text: `🎤 Voice pack set to ${voiceConfig.displayName}!`
                }],
                currentVoicePack: voiceGender,
                voicePackInfo: voiceConfig
            };
        }
    );
  • src/index.ts:56-59 (registration)
    Call to registerSettingsTools(server) which includes the set_voice_pack tool, in the main server setup for Smithery deployment.
    registerAchievementTools(server);
    registerSettingsTools(server);
    registerStatsTools(server);
    registerGuideTools(server);
  • run-server.ts:31-33 (registration)
    Call to registerSettingsTools(server) which includes the set_voice_pack tool, in the stdio server entry point.
    registerAchievementTools(server);
    registerSettingsTools(server);
    registerStatsTools(server);
Behavior4/5

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

Annotations indicate this is not read-only, destructive, idempotent, or open-world, but the description adds valuable behavioral context beyond annotations: it specifies the effect ('sets the default voice pack for all subsequent achievement sounds'), persistence ('persists for the session until changed'), and details about sound counts (15 for male, 16 for female), which helps the agent understand the tool's impact without contradictions.

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 supporting details in a logical flow (male/female specifics, persistence). Every sentence adds value without waste, making it efficient and well-structured for quick comprehension.

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 low complexity (1 parameter, no output schema), the description is mostly complete, covering purpose, usage, and behavioral effects. However, it lacks explicit mention of error cases or prerequisites (e.g., if the tool requires specific permissions), leaving a minor gap in full contextual coverage.

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 'voiceGender' parameter with enum values and examples. The description adds minimal extra meaning by listing specific sound examples (e.g., 'EXCELLENT', 'HEADSHOT'), but this is redundant with schema details, so it meets the baseline of 3 without significantly enhancing parameter understanding.

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 ('Switch between Male and Female announcer voice packs'), the resource ('voice packs'), and distinguishes it from siblings by specifying it sets the default for achievement sounds, unlike tools like 'get_voice_pack_info' or 'play_enhanced_quake_sound' which are read-only or play specific sounds.

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 ('sets the default voice pack for all subsequent achievement sounds') and mentions persistence ('The setting persists for the session until changed'), but does not explicitly state when not to use it or name alternatives like 'test_voice_packs' for previewing sounds.

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