Skip to main content
Glama
Ripnrip

Quake Coding Arena MCP

by Ripnrip

get_enhanced_achievement_stats

Read-onlyIdempotent

Retrieve detailed session statistics and achievement progress tracking for the Quake Coding Arena MCP server, including streak data, category breakdowns, and performance metrics.

Instructions

📊 Retrieve comprehensive session statistics and achievement progress. Returns total achievements played, category breakdown, session duration, current voice pack, volume setting, favorite category, current streak, longest streak, and achievements per minute rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_dummyNoNo parameters required. This tool returns session statistics without requiring any input.

Implementation Reference

  • The handler function that executes the tool logic, computing session duration and returning formatted statistics including total achievements, category stats, voice pack, and achievements per minute.
    async () => {
        const sessionMinutes = Math.floor((Date.now() - new Date(enhancedStats.sessionStart).getTime()) / 60000);
    
        return {
            content: [{
                type: "text",
                text: `📊 Enhanced arena statistics retrieved!\nTotal achievements: ${enhancedStats.totalAchievements}\nSession time: ${sessionMinutes} minutes\nCurrent voice: ${enhancedStats.voicePack}`
            }],
            stats: {
                ...enhancedStats,
                sessionMinutes,
                achievementsPerMinute: sessionMinutes > 0 ? enhancedStats.totalAchievements / sessionMinutes : 0
            }
        };
    }
  • The tool's input schema (no required params), description, and annotations defining its behavior and hints.
    {
        description: "📊 Retrieve comprehensive session statistics and achievement progress. Returns total achievements played, category breakdown, session duration, current voice pack, volume setting, favorite category, current streak, longest streak, and achievements per minute rate.",
        inputSchema: {
            // No parameters required for this tool
            _dummy: z.string().optional().describe("No parameters required. This tool returns session statistics without requiring any input.")
        },
        annotations: {
            title: "📊 Get Achievement Stats",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
        }
    },
  • The MCP server.registerTool invocation that registers 'get_enhanced_achievement_stats' with its schema and handler function.
    server.registerTool(
        "get_enhanced_achievement_stats",
        {
            description: "📊 Retrieve comprehensive session statistics and achievement progress. Returns total achievements played, category breakdown, session duration, current voice pack, volume setting, favorite category, current streak, longest streak, and achievements per minute rate.",
            inputSchema: {
                // No parameters required for this tool
                _dummy: z.string().optional().describe("No parameters required. This tool returns session statistics without requiring any input.")
            },
            annotations: {
                title: "📊 Get Achievement Stats",
                readOnlyHint: true,
                destructiveHint: false,
                idempotentHint: true,
                openWorldHint: false
            }
        },
        async () => {
            const sessionMinutes = Math.floor((Date.now() - new Date(enhancedStats.sessionStart).getTime()) / 60000);
    
            return {
                content: [{
                    type: "text",
                    text: `📊 Enhanced arena statistics retrieved!\nTotal achievements: ${enhancedStats.totalAchievements}\nSession time: ${sessionMinutes} minutes\nCurrent voice: ${enhancedStats.voicePack}`
                }],
                stats: {
                    ...enhancedStats,
                    sessionMinutes,
                    achievementsPerMinute: sessionMinutes > 0 ? enhancedStats.totalAchievements / sessionMinutes : 0
                }
            };
        }
    );
  • src/index.ts:58-58 (registration)
    Invocation of registerStatsTools in the main MCP server setup (src/index.ts), which registers the tool.
    registerStatsTools(server);
  • run-server.ts:33-33 (registration)
    Invocation of registerStatsTools in the stdio server entry point (run-server.ts), which registers the tool.
    registerStatsTools(server);
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds valuable context by listing specific return fields (e.g., session duration, current streak, achievements per minute rate), which helps the agent understand what data to expect beyond just 'statistics'. It does not contradict annotations, as 'retrieve' aligns with read-only behavior.

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 that front-loads the purpose ('Retrieve comprehensive session statistics and achievement progress') and follows with a detailed list of return values. Every element adds value by specifying what data is included, with no wasted words or redundancy.

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 complexity (retrieving multiple stats), annotations provide good safety coverage, and the description details the return fields comprehensively. However, there is no output schema, so the description must fully explain return values, which it does by listing them explicitly. It could improve by mentioning data formats or units (e.g., duration in minutes), but it is largely complete for a read-only stats tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter '_dummy' documented as 'No parameters required'. The description reinforces this by stating 'Returns session statistics without requiring any input', adding clarity that no user input is needed. This compensates for the dummy parameter's potential confusion, earning a score above the baseline of 3.

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 verb 'retrieve' and the resource 'comprehensive session statistics and achievement progress', making the purpose specific. It distinguishes from siblings like 'list_enhanced_achievements' by focusing on aggregated stats rather than listing individual achievements, and from 'get_ai_usage_guide' or 'get_enhanced_achievement_guide' by providing data rather than instructions.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention when this tool is appropriate (e.g., for summary reports) or when to prefer other tools like 'list_enhanced_achievements' for detailed lists, leaving usage context implied at best.

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