Skip to main content
Glama
CodeDreamer06

MonkeyType MCP Server

get_configuration

Retrieve server configuration settings for the MonkeyType MCP Server to access typing test data, user profiles, leaderboards, and statistics.

Instructions

Get server configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_configuration' tool. It calls the MonkeyType API endpoint '/configuration' using the shared callMonkeyTypeApi helper and returns the JSON-formatted result.
    case "get_configuration": {
      const result = await callMonkeyTypeApi('/configuration', 'GET', apiKey);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod schema definition for the 'get_configuration' tool input, which extends BaseApiSchema and requires no parameters.
    const GetConfigurationSchema = BaseApiSchema.extend({});
  • server.js:270-274 (registration)
    Registration of the 'get_configuration' tool in the listTools response, including name, description, and input schema.
    {
      name: "get_configuration",
      description: "Get server configuration",
      inputSchema: zodToJsonSchema(GetConfigurationSchema),
    },
  • Shared helper function used by the 'get_configuration' handler (and all other tools) to make authenticated API calls to the MonkeyType server.
    async function callMonkeyTypeApi(endpoint, method, apiKey, params = {}, data = null) {
      try {
        const headers = {
          'Authorization': `ApeKey ${apiKey}`,
          'Content-Type': 'application/json',
          'User-Agent': 'MonkeyType-MCP-Server/1.0.0'
        };
    
        const config = {
          headers,
          timeout: 30000,
          validateStatus: status => status < 500
        };
    
        if (method === 'GET' && Object.keys(params).length > 0) {
          config.params = params;
        }
    
        let response;
        if (method === 'GET') {
          response = await axios.get(`${MONKEYTYPE_API_BASE_URL}${endpoint}`, config);
        } else if (method === 'POST') {
          response = await axios.post(`${MONKEYTYPE_API_BASE_URL}${endpoint}`, data, config);
        }
    
        return response.data;
      } catch (error) {
        console.error(`Error calling MonkeyType API: ${error.message}`);
        if (error.response) {
          return { 
            error: error.response.data, 
            statusCode: error.response.status 
          };
        }
        return { 
          error: error.message 
        };
      }
    }
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 server configuration' implies a read operation, but it doesn't specify what the configuration includes, whether it's cached, requires authentication, or has rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise with a single sentence ('Get server configuration'), which is front-loaded and wastes no words. For a simple tool with no parameters, this brevity is appropriate and efficient.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'configuration' includes, the return format, or how it differs from sibling tools. For a tool in a context with many similar siblings, more detail is needed to ensure the agent can use it correctly.

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, meaning no parameters are documented in the schema. The description doesn't add parameter details, but since there are no parameters, this is acceptable. A baseline of 4 is appropriate as the description doesn't need to compensate for missing param info.

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 states what the tool does ('Get server configuration') with a clear verb and resource, but it's vague about what 'configuration' entails. It doesn't distinguish this tool from siblings like 'get_stats' or 'get_typing_stats', which might also retrieve server-related data. The purpose is understandable 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. With siblings like 'get_stats' and 'get_typing_stats' that might overlap in retrieving server data, there's no indication of context, prerequisites, or exclusions. It's a basic statement without usage 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