Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testMattermostConnection

Idempotent

Tests a Mattermost webhook connection by sending a notification to verify the provided webhook URL and optional channel or username settings.

Instructions

POST /notification.testMattermostConnection

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "webhookUrl": "<webhookUrl>"
    },
    "name": "notification-testMattermostConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNo
usernameNo
webhookUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the outbound-network and repeatability profile is covered. The description adds nothing beyond that: it does not disclose whether a real message is delivered to the channel, whether credentials are validated, or what a failure looks like — the most important behavior for a "test" tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single line is short but not concise in a useful sense — it is under-specified rather than economical. Front-loading is irrelevant when the whole content is an endpoint path with no prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, one required, no output schema, and only two shallow annotations, the description carries most of the disclosure burden and supplies essentially none. An agent cannot tell what happens on invocation or what a success response means from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three parameters, so the description is the only place meaning could be added, and it adds none. It says nothing about whether channel/username override the webhook's defaults or what format webhookUrl must take, leaving the agent with only self-explanatory parameter names.

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

Purpose2/5

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

The description is only the raw endpoint path "POST /notification.testMattermostConnection", which merely restates the tool name in URL form. It does not say what a "test connection" actually does (e.g. whether it posts a live test message to the Mattermost channel or only validates the webhook URL).

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?

There is no when-to-use guidance, no prerequisites, and no mention of sibling alternatives such as notification-createMattermost or the other provider test tools. The agent must infer from the name alone that this validates Mattermost config rather than creating or updating it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools