Skip to main content
Glama
Ripnrip

Quake Coding Arena MCP

by Ripnrip

list_enhanced_achievements

Read-onlyIdempotent

Retrieve available achievements and categories for coding milestones, with optional filtering by achievement type like streaks, multi-kills, or team events.

Instructions

📋 List all available enhanced achievements and their categories. Returns achievement names, categories, and thresholds. Useful for discovering available achievements or filtering by category type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo🎯 Filter achievements by category. Options: 'streak' (kill streak achievements like RAMPAGE, DOMINATING), 'quality' (quality-based achievements like EXCELLENT, PERFECT), 'multi' (multi-kill achievements like WICKED SICK, HEADSHOT), 'game' (game state announcements like FIRST BLOOD, HUMILIATION), 'team' (team events like PREPARE TO FIGHT, PLAY). If omitted, returns all achievements. Examples: 'streak', 'multi'

Implementation Reference

  • The core handler function for the 'list_enhanced_achievements' tool. It extracts optional category filter, filters and sorts achievements from ENHANCED_ACHIEVEMENTS, and returns a structured list with success status, message, achievements array, and total count.
    async listEnhancedAchievements(args) {
      const { category } = args;
    
      let achievements = Object.entries(ENHANCED_ACHIEVEMENTS);
    
      if (category) {
        achievements = achievements.filter(([_, info]) => info.category === category);
      }
    
      const sortedAchievements = achievements.sort((a, b) => {
        // Sort by category first, then by threshold
        if (a[1].category !== b[1].category) {
          return a[1].category.localeCompare(b[1].category);
        }
        return a[1].threshold - b[1].threshold;
      });
    
      const list = sortedAchievements.map(([name, info]) => ({
        name: name,
        file: info.file,
        category: info.category,
        threshold: info.threshold
      }));
    
      return {
        success: true,
        message: category
          ? `📋 Found ${list.length} enhanced ${category} achievements!`
          : `📋 Found all ${list.length} enhanced achievements!`,
        achievements: list,
        total: list.length
      };
    }
  • The JSON schema definition for the 'list_enhanced_achievements' tool, including name, description, and input schema with optional 'category' enum filter.
    {
      name: "list_enhanced_achievements",
      description: "📋 List all available enhanced achievements with detailed info",
      inputSchema: {
        type: "object",
        properties: {
          category: {
            type: "string",
            description: "🎯 Filter by category (streak, quality, multi, game, team, powerup)",
            enum: ["streak", "quality", "multi", "game", "team", "powerup"],
          },
        },
      },
    },
  • index.js:232-233 (registration)
    Registration/dispatch in the CallToolRequestSchema handler switch statement, routing calls to the listEnhancedAchievements method.
    case "list_enhanced_achievements":
      return await this.listEnhancedAchievements(args);
  • Alternative registration of the tool using server.registerTool, including schema (using Zod) and inline handler function that lists achievements similarly.
    server.registerTool(
        "list_enhanced_achievements",
        {
            description: "📋 List all available enhanced achievements and their categories. Returns achievement names, categories, and thresholds. Useful for discovering available achievements or filtering by category type.",
            inputSchema: {
                category: z.enum(["streak", "quality", "multi", "game", "team"]).optional().describe("🎯 Filter achievements by category. Options: 'streak' (kill streak achievements like RAMPAGE, DOMINATING), 'quality' (quality-based achievements like EXCELLENT, PERFECT), 'multi' (multi-kill achievements like WICKED SICK, HEADSHOT), 'game' (game state announcements like FIRST BLOOD, HUMILIATION), 'team' (team events like PREPARE TO FIGHT, PLAY). If omitted, returns all achievements. Examples: 'streak', 'multi'"),
            },
            annotations: {
                title: "📋 List Achievements",
                readOnlyHint: true,
                destructiveHint: false,
                idempotentHint: true,
                openWorldHint: false
            }
        },
        async ({ category }) => {
            const achievements = category
                ? Object.entries(ENHANCED_ACHIEVEMENTS).filter(([_, info]) => info.category === category)
                : Object.entries(ENHANCED_ACHIEVEMENTS);
    
            const achievementList = achievements.map(([name, info]) =>
                `🏆 ${name} (${info.category}, threshold: ${info.threshold})`
            ).join('\n');
    
            return {
                content: [{
                    type: "text",
                    text: `📋 Available achievements:\n${achievementList}`
                }],
                achievements: achievements.map(([name, info]) => ({
                    name,
                    ...info
                })),
                total: achievements.length,
                category
            };
        }
    );
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent, and closed-world behavior. The description adds value by specifying the return format ('Returns achievement names, categories, and thresholds') and the optional filtering capability, which are not covered by annotations. No contradiction with 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 front-loaded with the core purpose in the first sentence, followed by additional context in a second sentence. Both sentences are necessary and efficient, with no redundant information, making it appropriately sized and well-structured.

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 (one optional parameter), rich annotations, and 100% schema coverage, the description is largely complete. However, without an output schema, it could benefit from more detail on the return structure (e.g., format of thresholds), though it adequately covers the tool's purpose and usage.

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 parameter 'category' fully documented in the schema including enum values and examples. The description mentions filtering by category type but does not add meaningful semantic details beyond what the schema provides, meeting the baseline for high schema coverage.

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 ('List') and resource ('enhanced achievements and their categories'), specifying it returns achievement names, categories, and thresholds. It distinguishes from siblings by focusing on listing all available achievements, unlike tools like 'get_enhanced_achievement_stats' or 'random_enhanced_achievement'.

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 discovering available achievements or filtering by category type'), but does not explicitly state when not to use it or name specific alternatives among siblings. It implies usage for listing vs. other achievement-related operations.

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