Skip to main content
Glama
CodeDreamer06

MonkeyType MCP Server

get_typing_stats

Retrieve global typing statistics from MonkeyType to analyze typing performance metrics and trends.

Instructions

Get global typing statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the get_typing_stats tool, which calls the MonkeyType API endpoint '/public/typingStats' and returns the result as JSON.
    case "get_typing_stats": {
      const result = await callMonkeyTypeApi('/public/typingStats', 'GET', apiKey);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod schema definition for the get_typing_stats tool input (empty object since no parameters).
    const GetTypingStatsSchema = BaseApiSchema.extend({});
  • server.js:227-231 (registration)
    Registration of the get_typing_stats tool in the list of available tools.
    {
      name: "get_typing_stats",
      description: "Get global typing statistics",
      inputSchema: zodToJsonSchema(GetTypingStatsSchema),
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('get'), but doesn't mention any behavioral traits such as rate limits, authentication needs, data freshness, or what 'global' entails. This leaves significant gaps for a tool with no annotation support.

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 no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy for an agent to parse quickly.

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 'global typing statistics' includes (e.g., metrics, time ranges, aggregation), nor does it provide context on behavior or output. For a tool in this environment, more detail is needed to be fully helpful.

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 inputs. The description doesn't need to add parameter details, and it doesn't contradict the schema. A baseline of 4 is appropriate as no parameters exist to explain.

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 global typing statistics' clearly states the action (get) and resource (typing statistics), but it's vague about what 'global' means and doesn't differentiate from sibling tools like 'get_stats' or 'get_speed_histogram'. It provides basic purpose 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?

No guidance is provided on when to use this tool versus alternatives like 'get_stats' or 'get_speed_histogram'. The description implies a global scope but doesn't specify contexts 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