Skip to main content
Glama
CodeDreamer06

MonkeyType MCP Server

get_speed_histogram

Retrieve typing speed distribution data for analyzing performance patterns across different languages and test modes.

Instructions

Get speed histogram data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageYesTarget language for the speed histogram (e.g., 'english')
modeYesTyping mode (e.g., 'time', 'words')
mode2YesSecondary mode parameter (e.g., '60' for time mode)

Implementation Reference

  • Handler for the 'get_speed_histogram' tool that constructs parameters from input arguments and calls the MonkeyType API endpoint '/public/speedHistogram' to retrieve speed histogram data.
    case "get_speed_histogram": {
      const params = { 
        language: args.language,
        mode: args.mode,
        mode2: args.mode2 
      };
      
      const result = await callMonkeyTypeApi('/public/speedHistogram', 'GET', apiKey, params);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod input schema for the 'get_speed_histogram' tool, defining required parameters: language, mode (enum), and mode2.
    const GetSpeedHistogramSchema = BaseApiSchema.extend({
      language: z.string().describe("Target language for the speed histogram (e.g., 'english')"),
      mode: z.enum(["time", "words", "quote", "custom", "zen"]).describe("Typing mode (e.g., 'time', 'words')"),
      mode2: z.string().describe("Secondary mode parameter (e.g., '60' for time mode)")
    });
  • server.js:222-226 (registration)
    Registration of the 'get_speed_histogram' tool in the listTools response, including name, description, and input schema reference.
    {
      name: "get_speed_histogram",
      description: "Get speed histogram data",
      inputSchema: zodToJsonSchema(GetSpeedHistogramSchema),
    },
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. 'Get speed histogram data' implies a read-only operation but doesn't specify whether it requires authentication, how data is returned (e.g., format, pagination), or any rate limits. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it appropriately concise. However, it lacks front-loading of critical details like purpose differentiation or usage context, which slightly reduces its effectiveness despite the brevity.

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?

Given the tool's complexity (3 required parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what the histogram data represents, how it's structured, or any dependencies, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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 clear descriptions for all parameters (language, mode, mode2), including an enum for mode. The description adds no parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without adding value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description 'Get speed histogram data' states the basic action (get) and resource (speed histogram data), but it's vague about what 'speed histogram data' entails and doesn't distinguish this tool from similar-sounding siblings like 'get_typing_stats' or 'get_stats'. It provides minimal differentiation beyond the tool name.

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 offers no guidance on when to use this tool versus alternatives like 'get_typing_stats' or 'get_stats', nor does it mention prerequisites or context for retrieving histogram data. Usage is implied only by the tool name and parameters, with no explicit when/when-not instructions.

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