Skip to main content
Glama

get_game

Retrieve detailed information about a specific Twitch game by providing its name. This tool accesses the Twitch API to fetch game data for analysis or integration purposes.

Instructions

特定のゲームの情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesゲーム名

Implementation Reference

  • Handler function that implements the get_game tool by fetching game details from Twitch API using the game name.
    export async function handleGetGame(apiClient: ApiClient, args: { name: string }) {
      const game = await apiClient.games.getGameByName(args.name);
      if (!game) {
        throw new McpError(ErrorCode.InvalidParams, `Game "${args.name}" not found`);
      }
    
      return formatResponse({
        id: game.id,
        name: game.name,
        boxArtUrl: game.boxArtUrl,
      });
    }
  • Tool schema definition for get_game, specifying input as object with required 'name' string.
    {
      name: 'get_game',
      description: '特定のゲームの情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'ゲーム名',
          },
        },
        required: ['name'],
      },
    },
  • src/index.ts:101-104 (registration)
    Registration of the get_game tool handler in the switch statement for CallToolRequest.
    case 'get_game':
      return await handleGetGame(this.apiClient, {
        name: args.name as string
      });
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 what the tool does without behavioral details. It doesn't disclose if this is a read-only operation, requires authentication, has rate limits, or what the return format might be (e.g., JSON structure, error handling). This is inadequate 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 in Japanese with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core purpose without unnecessary elaboration.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what information is returned (e.g., game details, metadata), potential errors, or behavioral context, leaving significant gaps for the agent to infer usage.

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 schema description coverage is 100%, with the parameter 'name' clearly documented as 'ゲーム名' (game name) in the schema. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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/retrieve) and resource '特定のゲームの情報' (information of a specific game), making the purpose understandable. However, it doesn't differentiate from siblings like 'get_top_games' or 'search_categories' which also retrieve game-related information, 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. It doesn't mention prerequisites, exclusions, or compare to siblings like 'get_top_games' (for trending games) or 'search_categories' (for broader searches), leaving the agent with no contextual usage information.

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/mtane0412/twitch-mcp-server'

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