Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateMattermost

Idempotent

Updates a Mattermost notification configuration in Dokploy, including webhook URL, channel, username, and event alert settings.

Instructions

POST /notification.updateMattermost

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": {
      "notificationId": "<notificationId>",
      "mattermostId": "<mattermostId>"
    },
    "name": "notification-updateMattermost"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
channelNo
usernameNo
appDeployNo
webhookUrlNo
mattermostIdYes
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
notificationIdYes
organizationIdNo
serverThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations supply openWorldHint=true and idempotentHint=true, so the agent knows calls are idempotent and reach an external Mattermost endpoint. The description adds nothing beyond the route string: it does not say whether omitted fields are left untouched or cleared, whether webhookUrl changes require re-testing, or what permissions are needed for a mutation with 15 fields.

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?

It is short, but brevity here comes from under-specification rather than efficiency; a bare route string earns almost no place as guidance. There is no front-loading of purpose or constraints because no content exists beyond the endpoint path.

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?

For a 15-parameter mutation tool with no output schema and only two weak annotation hints, the description should carry substantial weight and carries none. An agent cannot determine update semantics, required-field behavior, or the effect of the 13 optional fields from this definition.

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

Parameters1/5

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

Schema description coverage is 0% across 15 parameters, so the schema names alone carry all meaning and the description must compensate — it does not. Nothing explains whether event boolean flags (appDeploy, databaseBackup, serverThreshold, etc.) enable or disable notifications, or how mattermostId/notificationId relate.

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 just the HTTP route 'POST /notification.updateMattermost', which restates the tool name rather than stating the operation. It confirms this is an update to a Mattermost notification config, but that is inferable from the name alone, and it gives no indication of what is updated or what the tool returns.

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: nothing distinguishes this from siblings such as notification-createMattermost (creating a new config) or notification-testMattermostConnection (validating one). The agent must infer the create-vs-update distinction purely from naming conventions.

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