Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateSlack

Idempotent

Modify a Slack notification configuration in Dokploy by updating channel, webhook URL, and alert event settings to keep team alerts routed correctly.

Instructions

POST /notification.updateSlack

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>",
      "slackId": "<slackId>"
    },
    "name": "notification-updateSlack"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior2/5

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

Annotations already state idempotentHint=true and openWorldHint=true, so the description adds nothing beyond them. It does not disclose what gets overwritten, whether fields are optional partial updates, or how the target notification is identified, which matters for a mutation tool.

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

Conciseness1/5

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

The single line is under-specification rather than conciseness; no substantive content is front-loaded because there is no content at all.

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 14-parameter mutation tool with no output schema and no parameter documentation, the description is completely inadequate for calling it correctly.

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 14 parameters, and the description provides no parameter meaning whatsoever. Names like 'serverThreshold', 'dokployRestart', and the required 'slackId'/'notificationId' pair are left entirely unexplained.

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 HTTP route 'POST /notification.updateSlack', which restates the tool name rather than explaining what the operation does. An agent can infer it mutates a Slack notification config, but there is no verb or resource framing beyond that.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance at all on when to use this versus siblings such as notification-createSlack or the other notification-update* variants. Nothing indicates prerequisites, required IDs, or when-not to use 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