Skip to main content
Glama
in2out

Mattermost S MCP

by in2out

mattermost_list_webhooks

View registered Mattermost webhook channels to manage communication endpoints for sending messages via the MCP protocol.

Instructions

등록된 Mattermost 웹훅 채널 목록을 확인합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'mattermost_list_webhooks' tool. It loads the config, extracts default channel and list of webhooks, and returns formatted JSON response.
    async listWebhooks() {
      const config = this.loadConfig();
      const result = {
        default: config.default_channel || null,
        channels: config.webhooks.map((w) => ({
          channel: w.channel,
          description: w.description || "",
        })),
      };
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Input schema for the tool, which requires no parameters (empty object).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • index.js:77-84 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining name, description, and input schema.
    {
      name: "mattermost_list_webhooks",
      description: "등록된 Mattermost 웹훅 채널 목록을 확인합니다.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • index.js:125-127 (registration)
    Dispatch/registration in the CallToolRequestSchema switch statement, routing to the listWebhooks handler.
    case "mattermost_list_webhooks":
      return await this.listWebhooks();
  • Helper method used by the handler to load the webhooks configuration from YAML file.
    loadConfig() {
      try {
        const fileContents = readFileSync(CONFIG_PATH, "utf8");
        const config = yaml.load(fileContents);
    
        if (!config || !config.webhooks || !Array.isArray(config.webhooks)) {
          throw new Error("Invalid config structure");
        }
    
        return config;
      } catch (error) {
        throw new Error(`Failed to load config: ${error.message}`);
      }
    }
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 '확인합니다' (check/verify) implies a read-only operation, the description doesn't explicitly state whether this requires authentication, what permissions are needed, how results are returned, or any rate limits. It provides minimal behavioral context beyond the basic action.

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 Korean that directly states the tool's purpose without any unnecessary words or structural complexity. It's appropriately sized for a simple list operation with no parameters.

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?

For a zero-parameter list operation with no output schema, the description adequately explains what the tool does. However, without annotations covering behavioral aspects like authentication requirements or response format, and with sibling tools that aren't differentiated, there are clear contextual gaps that prevent higher completeness.

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 with 100% schema description coverage, so the schema fully documents the lack of inputs. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. This meets the baseline expectation for zero-parameter tools.

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 ('확인합니다' - check/verify) and resource ('등록된 Mattermost 웹훅 채널 목록' - registered Mattermost webhook channel list), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like mattermost_send_message or mattermost_set_default, 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 the sibling tools mattermost_send_message or mattermost_set_default. There's no mention of alternatives, prerequisites, or specific contexts where this tool is appropriate versus others.

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