Skip to main content
Glama
CodeDreamer06

MonkeyType MCP Server

get_stats

Retrieve typing statistics for a user from MonkeyType, including test data, accuracy metrics, and performance insights.

Instructions

Get user's typing statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_stats' tool. Calls the MonkeyType API endpoint '/users/stats' with GET method using the provided API key and returns the JSON response as text content.
    case "get_stats": {
      const result = await callMonkeyTypeApi('/users/stats', 'GET', apiKey);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod schema definition for 'get_stats' tool input, extending BaseApiSchema with no additional parameters (empty object).
    const GetStatsSchema = BaseApiSchema.extend({});
  • server.js:178-182 (registration)
    Registration of the 'get_stats' tool in the tools list provided to ListToolsRequest, including name, description, and input schema.
    {
      name: "get_stats",
      description: "Get user's typing statistics",
      inputSchema: zodToJsonSchema(GetStatsSchema),
    },
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. It states it's a read operation ('Get'), but doesn't mention authentication needs, rate limits, what specific stats are returned, or any side effects. For a stats tool with zero annotation coverage, this is insufficient.

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 simple tool and gets straight to the point without unnecessary elaboration.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what typing statistics are returned (e.g., speed, accuracy, duration), how they're formatted, or any behavioral context. For a stats retrieval tool, this leaves significant gaps.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to compensate for any parameter gaps, making it adequate for this parameterless tool.

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 user's typing statistics' clearly states the verb ('Get') and resource ('typing statistics'), but it's vague about scope and doesn't distinguish from sibling tools like 'get_typing_stats' which appears to serve a similar purpose. The description is functional but lacks specificity.

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_typing_stats' or other stats-related tools. There's no mention of prerequisites, context, or exclusions, leaving the agent with no usage direction.

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