Skip to main content
Glama
in2out

Mattermost S MCP

by in2out

mattermost_set_default

Set a specified channel as the default webhook for sending messages to Mattermost through MCP integration.

Instructions

지정한 채널을 기본 웹훅으로 설정합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes기본으로 설정할 채널명

Implementation Reference

  • The handler function that validates the channel, checks if it exists in config, sets it as default_channel, saves the config, and returns a success message.
    async setDefault(channel) {
      if (!channel || typeof channel !== "string") {
        throw new Error("channel 인자가 필요합니다.");
      }
    
      const config = this.loadConfig();
      const channelExists = config.webhooks.some((w) => w.channel === channel);
    
      if (!channelExists) {
        throw new Error(`등록되지 않은 채널입니다: ${channel}`);
      }
    
      config.default_channel = channel;
      this.saveConfig(config);
    
      return {
        content: [
          {
            type: "text",
            text: `기본 채널이 '${channel}' 으로 설정되었습니다.`,
          },
        ],
      };
    }
  • Input schema defining the required 'channel' string parameter for the tool.
    inputSchema: {
      type: "object",
      properties: {
        channel: {
          type: "string",
          description: "기본으로 설정할 채널명",
        },
      },
      required: ["channel"],
    },
  • index.js:85-98 (registration)
    Tool definition registered in the ListToolsRequest handler, including name, description, and input schema.
    {
      name: "mattermost_set_default",
      description: "지정한 채널을 기본 웹훅으로 설정합니다.",
      inputSchema: {
        type: "object",
        properties: {
          channel: {
            type: "string",
            description: "기본으로 설정할 채널명",
          },
        },
        required: ["channel"],
      },
    },
  • index.js:128-130 (registration)
    Dispatch to the setDefault handler in the CallToolRequest switch statement.
    case "mattermost_set_default":
      return await this.setDefault(args.channel);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While '설정합니다' (sets) implies a mutation operation, the description doesn't disclose important behavioral traits like whether this requires admin permissions, whether it overwrites existing default webhook settings, what happens if the channel doesn't exist, or any rate limits. For a mutation tool with zero annotation coverage, this represents a significant gap in behavioral 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, efficient sentence that gets straight to the point without any wasted words. It's appropriately sized for a single-parameter tool and front-loads the essential information about what the tool does.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after execution (success/failure indicators), doesn't mention permission requirements, and provides no information about the tool's behavior beyond the basic action. Given the complexity of a system configuration tool, more contextual information would be expected.

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 single parameter 'channel' well-documented in the schema as '기본으로 설정할 채널명' (channel name to set as default). The description doesn't add any meaningful parameter semantics beyond what the schema already provides, so it meets the baseline of 3 for high schema coverage situations.

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 action ('지정한 채널을...설정합니다' - sets the specified channel) and resource ('기본 웹훅' - default webhook), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like mattermost_list_webhooks or mattermost_send_message, which prevents 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. There's no mention of prerequisites (e.g., needing admin permissions), when this should be used instead of other webhook-related tools, or any exclusions. It simply states what the tool does without 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/in2out/mattermost-s-mcp'

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