Skip to main content
Glama

random-pokemon

Generate a random Pokémon using the model context protocol server Poke-MCP, perfect for discovering new Pokémon data without specific search criteria.

Instructions

Get a random Pokémon

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that generates a random Pokémon ID between 1 and 1000, fetches the Pokémon details, handles errors, and formats the response using formatPokemonResponse.
    async function getRandomPokemon(): Promise<PokemonResponse> {
      // There are currently around 1000+ Pokémon, but we'll limit to 1000 to be safe
      const randomId = Math.floor(Math.random() * 1000) + 1;
      const details = await getPokemonDetails(randomId.toString());
    
      if (!details) {
        return {
          content: [
            {
              type: "text",
              text: "Failed to retrieve a random Pokémon. Please try again.",
            },
          ],
        };
      }
    
      return formatPokemonResponse(details.pokemon, details.species);
    }
  • src/index.ts:319-325 (registration)
    Registers the 'random-pokemon' tool with no input parameters, a descriptive name, and an inline handler that delegates to the getRandomPokemon function.
      "random-pokemon",
      "Get a random Pokémon",
      {},
      async (_args, _extra) => {
        return await getRandomPokemon();
      }
    );
  • Type definition for the output response format used by the tool, consisting of text content blocks.
    export interface PokemonResponse {
      content: Array<{
        type: "text";
        text: string;
      }>;
      [key: string]: unknown;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, rate limits, what data is returned, or if there are any constraints on randomness. The description is minimal and lacks necessary context.

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 just three words, front-loading the core purpose without any wasted text. Every word earns its place, making it efficient for quick understanding.

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 'Get' entails (e.g., returns Pokémon data), the format of the result, or how randomness is implemented. For a tool with no structured support, more context is needed to guide the agent effectively.

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 appropriately doesn't mention parameters, which aligns with the schema. Baseline is 4 for 0 parameters as it correctly avoids unnecessary information.

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 'Get a random Pokémon' clearly states the action (Get) and resource (a random Pokémon), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'random-pokemon-by-type' or 'random-pokemon-from-region' which suggests more specific random selection methods.

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 its siblings. There's no mention of alternatives like 'pokemon-query' for specific searches or the other random tools for filtered random selection, leaving the agent without usage context.

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

Related 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/NaveenBandarage/poke-mcp'

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