Skip to main content
Glama

get_pokemon_cry

Retrieve Pokémon cry audio file URLs by providing the Pokémon name or ID number. Use this tool to access authentic Pokémon sounds for applications or analysis.

Instructions

ポケモンの鳴き声音声ファイルのURLを取得

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pokemonYesポケモン名またはID番号

Implementation Reference

  • The handler function that implements the get_pokemon_cry tool. It fetches Pokemon data from PokeAPI, constructs the cry URL using the Pokemon's ID, verifies the URL exists, and returns the cry information as JSON.
    private async getPokemonCry(pokemon: string) {
      try {
        const data = await this.fetchPokemonData(pokemon);
    
        // 鳴き声ファイルのURL(PokeAPI/cries リポジトリから)
        const cryUrl = `https://raw.githubusercontent.com/PokeAPI/cries/main/cries/pokemon/latest/${data.id}.ogg`;
    
        // URLが有効かチェック
        const response = await axios.head(cryUrl);
        if (response.status !== 200) {
          throw new Error(`鳴き声ファイルが見つかりません: ${cryUrl}`);
        }
    
        const cryInfo = {
          name: data.name,
          id: data.id,
          cry_url: cryUrl,
          format: "ogg",
          source: "PokeAPI/cries repository"
        };
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(cryInfo, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `エラー: ${error instanceof Error ? error.message : String(error)}`
            }
          ],
          isError: true
        };
      }
    }
  • The input schema for the get_pokemon_cry tool, specifying a required 'pokemon' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        pokemon: {
          type: "string",
          description: "ポケモン名またはID番号",
        },
      },
      required: ["pokemon"],
    },
  • src/index.ts:125-138 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema.
    {
      name: "get_pokemon_cry",
      description: "ポケモンの鳴き声音声ファイルのURLを取得",
      inputSchema: {
        type: "object",
        properties: {
          pokemon: {
            type: "string",
            description: "ポケモン名またはID番号",
          },
        },
        required: ["pokemon"],
      },
    },
  • src/index.ts:171-172 (registration)
    Dispatch logic in the CallToolRequest handler that routes calls to the getPokemonCry method.
    } else if (name === "get_pokemon_cry") {
      return await this.getPokemonCry(args.pokemon as string);
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 URL for a Pokémon's cry audio file, which implies a read-only operation, but it doesn't clarify aspects like error handling (e.g., what happens for invalid Pokémon names), response format, or any 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 a single, efficient sentence in Japanese that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to understand at a glance. There is no wasted information, earning it the highest score for conciseness.

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 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines, behavioral traits, and output specifics. While it meets the minimum for a simple tool, it doesn't provide enough context for optimal agent use, such as error cases or sibling tool differentiation.

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 parameter 'pokemon' documented as 'ポケモン名またはID番号' (Pokémon name or ID number). The description doesn't add any extra meaning beyond this, such as examples or constraints. Since the schema already fully describes the parameter, 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: 'ポケモンの鳴き声音声ファイルのURLを取得' (Get the URL of a Pokémon's cry audio file). It specifies the verb '取得' (get) and resource '鳴き声音声ファイルのURL' (cry audio file URL), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'play_pokemon_cry' (which might play the cry directly rather than returning a URL), so it doesn't reach the highest 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 sibling tools such as 'get_pokemon_info' or 'play_pokemon_cry', nor does it specify any context or prerequisites for usage. This lack of comparative or contextual information limits its effectiveness in guiding tool selection.

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/t-daiki96/poke_mcp'

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