Skip to main content
Glama

get_chat_settings

Retrieve chat configuration for a Twitch channel to view moderation settings and chat rules.

Instructions

チャット設定を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNameYesTwitchチャンネル名

Implementation Reference

  • The handler function that implements the core logic: retrieves the Twitch user by channel name, fetches chat settings using the API, and returns a formatted response with settings like emote-only mode, slow mode, etc.
    export async function handleGetChatSettings(apiClient: ApiClient, args: { channelName: string }) {
      const user = await getUserByName(apiClient, args.channelName);
      const settings = await apiClient.chat.getSettings(user.id);
    
      return formatResponse({
        emoteOnlyModeEnabled: settings.emoteOnlyModeEnabled,
        followerOnlyModeEnabled: settings.followerOnlyModeEnabled,
        followerOnlyModeDelay: settings.followerOnlyModeDelay,
        slowModeEnabled: settings.slowModeEnabled,
        slowModeDelay: settings.slowModeDelay,
        subscriberOnlyModeEnabled: settings.subscriberOnlyModeEnabled,
        uniqueChatModeEnabled: settings.uniqueChatModeEnabled,
      });
    }
  • The tool definition including name, description, and input schema requiring a 'channelName' string parameter.
    {
      name: 'get_chat_settings',
      description: 'チャット設定を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          channelName: {
            type: 'string',
            description: 'Twitchチャンネル名',
          },
        },
        required: ['channelName'],
      },
    },
  • src/index.ts:142-145 (registration)
    The switch case in the CallToolRequest handler that routes 'get_chat_settings' calls to the handleGetChatSettings function.
    case 'get_chat_settings':
      return await handleGetChatSettings(this.apiClient, {
        channelName: args.channelName as string
      });
  • src/index.ts:15-15 (registration)
    Import statement that brings the handler function into the main server file for use in tool dispatching.
    import { handleGetChannelInfo, handleGetChatSettings } from './tools/handlers/channel.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 the action ('get chat settings') without explaining what chat settings include, whether this is a read-only operation, any authentication needs, rate limits, or what the response format might be. This leaves significant gaps for an agent to understand the tool's 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 extremely concise—a single sentence that directly states the tool's purpose without any fluff or redundant information. It is front-loaded and wastes no words, 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 complexity of a tool that retrieves settings (which could involve permissions or detailed data), the description is insufficient. With no annotations, no output schema, and minimal behavioral context, it doesn't provide enough information for an agent to fully understand how to use this tool effectively compared to its siblings.

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, clearly documenting the single required parameter 'channelName' as a Twitch channel name. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, so it meets the baseline for high schema coverage without adding value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the purpose ('チャット設定を取得します' translates to 'Get chat settings'), which is a clear verb+resource combination. However, it doesn't differentiate this tool from its siblings (like get_channel_info or get_stream_info), leaving ambiguity about what specific 'chat settings' means in this context versus other channel-related data.

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. With siblings like get_channel_info and get_stream_info that might overlap in retrieving channel-related information, there's no indication of when chat settings are needed specifically, nor any prerequisites or exclusions mentioned.

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