Skip to main content
Glama

get_global_badges

Retrieve the list of global chat badges available on Twitch to identify and display user achievements and status indicators.

Instructions

グローバルチャットバッジのリストを取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'get_global_badges' tool. It retrieves global chat badges from the Twitch API and formats them into a structured response with badge IDs and version details including titles and image URLs.
    export async function handleGetGlobalBadges(apiClient: ApiClient) {
      const badges = await apiClient.chat.getGlobalBadges();
    
      return formatResponse(
        badges.map(badge => ({
          id: badge.id,
          versions: Object.fromEntries(
            badge.versions.map(version => [
              version.id,
              {
                title: version.title,
                imageUrl: version.getImageUrl(1),
              },
            ])
          ),
        }))
      );
    }
  • The schema definition for the 'get_global_badges' tool, specifying its name, description, and input schema (empty object since no parameters are required). This is part of the toolDefinitions array used for MCP tool listing.
    {
      name: 'get_global_badges',
      description: 'グローバルチャットバッジのリストを取得します',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:128-129 (registration)
    Registration of the tool handler in the main CallToolRequestSchema switch statement, dispatching calls to 'get_global_badges' to the handleGetGlobalBadges function.
    case 'get_global_badges':
      return await handleGetGlobalBadges(this.apiClient);
  • src/index.ts:19-19 (registration)
    Import statement bringing in the handleGetGlobalBadges handler function for use in the MCP server.
    import { handleGetGlobalEmotes, handleGetGlobalBadges } from './tools/handlers/chat.js';
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 only states what the tool does ('get a list'), without mentioning any behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the output format might be. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, clear sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it efficient and easy to parse for an AI agent.

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 for effective tool use. It does not explain what the returned list contains (e.g., badge details, formats), any limitations, or error conditions. For a tool that likely returns structured data, this omission reduces its utility for an AI agent.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description does not need to add parameter semantics, as there are none to document. This meets the baseline expectation for tools without parameters, as it avoids unnecessary details.

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 list of global chat badges). It specifies the verb '取得します' (get) and the resource 'グローバルチャットバッジのリスト' (list of global chat badges), making it easy to understand what the tool does. However, it does not explicitly differentiate from sibling tools like 'get_global_emotes' or 'get_channel_info', which slightly limits its clarity in a broader context.

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 does not mention any specific contexts, prerequisites, or exclusions, nor does it refer to sibling tools like 'get_global_emotes' for related data. This lack of usage context leaves the agent without clear direction on appropriate scenarios for 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/mtane0412/twitch-mcp-server'

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