Skip to main content
Glama
Traves-Theberge

Word of the Day MCP Server

get_random_word

Retrieve a random English word with its definition to expand vocabulary. Choose difficulty level (easy, medium, hard) for targeted learning.

Instructions

Get a random word with its definition for word of the day

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
difficultyNoDifficulty level of the random wordmedium

Implementation Reference

  • The main handler function for the 'get_random_word' tool. Parses args with schema, selects random word from difficulty-based lists, and delegates to getWordDefinition for full response.
    private async getRandomWord(args: unknown) {
      const { difficulty = 'medium' } = GetRandomWordArgsSchema.parse(args);
      
      // List of curated words by difficulty level
      const wordLists = {
        easy: [
          'happy', 'house', 'water', 'light', 'music', 'friend', 'smile', 'peace', 
          'dream', 'heart', 'love', 'hope', 'time', 'life', 'world', 'nature'
        ],
        medium: [
          'serendipity', 'eloquent', 'resilient', 'magnificent', 'innovative', 
          'perspective', 'authentic', 'curiosity', 'adventure', 'harmony', 
          'wisdom', 'courage', 'gratitude', 'compassion', 'creativity', 'balance'
        ],
        hard: [
          'ephemeral', 'ubiquitous', 'perspicacious', 'surreptitious', 'magnanimous',
          'obfuscate', 'ameliorate', 'propensity', 'vicissitude', 'perspicuity',
          'sesquipedalian', 'grandiloquent', 'pusillanimous', 'truculent', 'recalcitrant'
        ]
      };
    
      const words = wordLists[difficulty];
      const randomWord = words[Math.floor(Math.random() * words.length)];
      
      // Get the definition for the random word
      return await this.getWordDefinition({ word: randomWord, language: 'en' });
    }
  • Zod validation schema for get_random_word tool inputs: optional 'difficulty' enum.
    const GetRandomWordArgsSchema = z.object({
      difficulty: z.enum(['easy', 'medium', 'hard']).default('medium').optional(),
    });
  • src/index.ts:91-106 (registration)
    Tool metadata registration in ListTools response: name, description, inputSchema matching the Zod schema.
    {
      name: 'get_random_word',
      description: 'Get a random word with its definition for word of the day',
      inputSchema: {
        type: 'object',
        properties: {
          difficulty: {
            type: 'string',
            enum: ['easy', 'medium', 'hard'],
            description: 'Difficulty level of the random word',
            default: 'medium',
          },
        },
        required: [],
      },
    },
  • src/index.ts:119-120 (registration)
    Dispatch registration in CallToolRequest handler switch statement, routing to the getRandomWord method.
    case 'get_random_word':
      return await this.getRandomWord(args);
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 the tool returns a random word with its definition, but doesn't cover other behavioral traits such as rate limits, authentication needs, error handling, or whether the word changes per call. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operation.

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 that clearly states the tool's purpose without unnecessary words. It's front-loaded with the core function, making it easy to grasp quickly. However, it could be slightly more structured by explicitly noting the optional parameter, but overall it's concise and well-formed.

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 low complexity (one optional parameter) and no output schema, the description is minimally adequate. It covers what the tool does but lacks details on behavioral aspects like how randomness is implemented or what the return format includes. Without annotations or output schema, more context on the response structure would improve completeness, but it's not entirely incomplete.

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?

The input schema has 100% description coverage, with the single parameter 'difficulty' fully documented in the schema (including enum values and default). The description doesn't add any meaning beyond this, as it doesn't mention parameters at all. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 tool's purpose: 'Get a random word with its definition for word of the day'. It specifies the verb ('Get'), resource ('random word'), and additional output ('definition'), making the function unambiguous. However, it doesn't explicitly differentiate from the sibling tool 'get_word_definition', which likely fetches definitions for specific words rather than random ones, so it falls short of 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. It doesn't mention the sibling tool 'get_word_definition' or clarify scenarios where one might prefer a random word over a specific lookup. Usage is implied by the phrase 'word of the day', but this is vague and lacks explicit context or exclusions.

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/Traves-Theberge/Word_of_the_day'

If you have feedback or need assistance with the MCP directory API, please join our Discord server