Skip to main content
Glama
CodeDreamer06

MonkeyType MCP Server

get_streak

Retrieve typing streak data to track consecutive days of practice on MonkeyType, helping users monitor consistency and maintain motivation.

Instructions

Get user's typing streak information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the get_streak tool that calls the MonkeyType API endpoint /users/streak and returns the result as text.
    case "get_streak": {
      const result = await callMonkeyTypeApi('/users/streak', 'GET', apiKey);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • server.js:198-202 (registration)
    Registration of the get_streak tool in the list of tools provided to the LLM.
    {
      name: "get_streak",
      description: "Get user's typing streak information",
      inputSchema: zodToJsonSchema(GetStreakSchema),
    },
  • Zod schema definition for get_streak tool input, which takes no parameters.
    const GetStreakSchema = BaseApiSchema.extend({});
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. It states it 'gets' information, implying a read-only operation, but doesn't specify if it requires authentication, returns real-time or cached data, or handles errors. This is a significant gap for a tool with zero annotation coverage.

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 waste. It's front-loaded with the core purpose and appropriately sized for a simple tool, making it highly concise and well-structured.

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?

Given the tool's simplicity (0 params, no output schema), the description is minimally adequate. However, with no annotations and siblings that might overlap, it lacks context on behavior and usage, leaving gaps that could confuse an agent in a real scenario.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param details, which is appropriate, but it could hint at implicit inputs like user context. Baseline is 4 since no params exist.

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 the resource 'user's typing streak information', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from similar siblings like 'get_stats' or 'get_typing_stats', which might also provide streak-related data, preventing a perfect score.

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 siblings like 'get_stats' and 'get_typing_stats' that might overlap, there's no indication of context, prerequisites, or exclusions, leaving usage ambiguous.

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