Skip to main content
Glama
CodeDreamer06

MonkeyType MCP Server

get_personal_bests

Retrieve your personal best typing scores from MonkeyType to track progress across different modes like time trials, word tests, quotes, and zen typing.

Instructions

Get user's personal best typing scores

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMode for personal bests (time, words, quote, zen). Defaults to 'time'
mode2NoSecondary mode parameter for time mode (e.g., 15, 30, 60, 120). Defaults to '15'

Implementation Reference

  • Handler for get_personal_bests tool: constructs params with defaults for mode and mode2, calls the MonkeyType API endpoint '/users/personalBests', and returns the JSON result.
    case "get_personal_bests": {
      // Add required mode parameter
      const params = {
        mode: args.mode || "time", // Default to time mode if not specified
        mode2: args.mode2 || "15" // Default to 15 seconds if not specified (confirmed from previous change)
      };
      
      const result = await callMonkeyTypeApi('/users/personalBests', 'GET', apiKey, params);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod schema defining optional input parameters mode and mode2 for the get_personal_bests tool.
    const GetPersonalBestsSchema = BaseApiSchema.extend({
      mode: z.string().optional().describe("Mode for personal bests (time, words, quote, zen). Defaults to 'time'"),
      mode2: z.string().optional().describe("Secondary mode parameter for time mode (e.g., 15, 30, 60, 120). Defaults to '15'")
    });
  • server.js:168-172 (registration)
    Registration of the get_personal_bests tool in the list of tools returned by ListToolsRequest, including name, description, and input schema.
    {
      name: "get_personal_bests",
      description: "Get user's personal best typing scores",
      inputSchema: zodToJsonSchema(GetPersonalBestsSchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what happens if no personal bests exist. For a tool with no annotation coverage, 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 that states the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information, making it easy to parse quickly.

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

Completeness3/5

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

For a simple read operation with 2 parameters and no output schema, the description is minimally adequate. It states what the tool does but lacks context about authentication, error handling, or return format. With no annotations and no output schema, the description should ideally provide more behavioral context to be fully complete.

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 description mentions 'typing scores' which relates to the tool's purpose but doesn't explain the parameters. However, with 100% schema description coverage, the schema fully documents both parameters with descriptions and defaults. The description adds no parameter-specific information beyond what's in the schema, 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.

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('user's personal best typing scores'), making it immediately understandable. However, it doesn't differentiate from siblings like 'get_stats' or 'get_typing_stats' which might also retrieve user statistics, leaving some ambiguity about uniqueness.

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. With many sibling tools like 'get_stats' and 'get_typing_stats' that might overlap in functionality, there's no indication of when this specific tool is appropriate or what distinguishes it from similar options.

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