Skip to main content
Glama
CodeDreamer06

MonkeyType MCP Server

get_daily_leaderboard

Retrieve the daily typing test leaderboard from MonkeyType to view top performers by language, mode, and time period for competitive analysis.

Instructions

Get daily typing test leaderboard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoLanguage for the leaderboard
modeNoMode for the leaderboard (time, words, quote, zen)
mode2NoSecondary mode parameter (e.g., 15, 60, etc.)
skipNoNumber of entries to skip
limitNoNumber of entries to return

Implementation Reference

  • Handler implementation for the 'get_daily_leaderboard' tool. Builds query parameters from input arguments and calls the MonkeyType API endpoint '/leaderboards/daily' to fetch the daily leaderboard data.
    case "get_daily_leaderboard": {
      const params = {};
      if (args.language) params.language = args.language;
      if (args.mode) params.mode = args.mode;
      if (args.mode2) params.mode2 = args.mode2;
      if (args.skip) params.skip = args.skip;
      if (args.limit) params.limit = args.limit;
      
      const result = await callMonkeyTypeApi('/leaderboards/daily', 'GET', apiKey, params);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod input schema definition for the 'get_daily_leaderboard' tool, extending BaseApiSchema with optional parameters for language, mode, mode2, skip, and limit.
    const GetDailyLeaderboardSchema = BaseApiSchema.extend({
      language: z.string().optional().describe("Language for the leaderboard"),
      mode: z.string().optional().describe("Mode for the leaderboard (time, words, quote, zen)"),
      mode2: z.string().optional().describe("Secondary mode parameter (e.g., 15, 60, etc.)"),
      skip: z.number().optional().describe("Number of entries to skip"),
      limit: z.number().optional().describe("Number of entries to return")
    });
  • server.js:244-248 (registration)
    Registration of the 'get_daily_leaderboard' tool in the ListToolsRequestHandler response, including name, description, and input schema.
    {
      name: "get_daily_leaderboard",
      description: "Get daily typing test leaderboard",
      inputSchema: zodToJsonSchema(GetDailyLeaderboardSchema),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action. It doesn't describe what data is returned (e.g., format, fields), whether it's paginated, rate-limited, or requires authentication. For a read operation with 5 parameters, this leaves significant behavioral gaps.

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 with zero wasted words. It's appropriately sized for a straightforward retrieval tool and front-loads the core purpose immediately.

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

Completeness2/5

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

For a tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the leaderboard contains, how results are structured, or clarify the relationship between 'daily' and other leaderboard tools. The agent would need to guess about return values and proper usage context.

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%, so all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema descriptions. This meets the baseline expectation when 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 verb ('Get') and resource ('daily typing test leaderboard'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_leaderboard' or 'get_weekly_xp_leaderboard', which would require specifying what makes the 'daily' leaderboard unique.

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 guidance on when to use this tool versus alternatives like 'get_leaderboard' or 'get_weekly_xp_leaderboard'. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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/CodeDreamer06/MonkeytypeMCP'

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