Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateCustom

Idempotent

Updates a custom notification channel's endpoint, headers, and event toggles in Dokploy. Use it to adjust where alerts are sent and which deployment or backup events trigger them.

Instructions

POST /notification.updateCustom

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>",
      "customId": "<customId>"
    },
    "name": "notification-updateCustom"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
headersNo
customIdYes
endpointNo
appDeployNo
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
notificationIdYes
organizationIdNo
serverThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the bar is lower, but the description adds zero behavioral context. It does not mention that this is a mutation, which fields are replaced versus preserved, whether partial updates are allowed, or anything about the credential-bearing headers/endpoint being modified.

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 the brevity is under-specification rather than conciseness — a bare method-plus-path string with no front-loaded statement of intent. Nothing in the single fragment earns its place as an explanation.

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 14 parameters, 2 required, a nested object (headers), no output schema, and no destructiveHint to signal mutation semantics, this description is far too thin. An agent cannot determine what a call will change or what a minimally correct request looks like.

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, so the description must carry the load and it carries none. Nothing explains the event-toggle booleans (appDeploy, volumeBackup, dockerCleanup, serverThreshold, etc.), the headers map, or how customId and notificationId together identify the target.

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 "POST /notification.updateCustom" — it restates the tool name and HTTP verb without saying what is actually being updated or what a "custom" notification is. It distinguishes the resource family (custom vs. Slack/Email/Discord siblings) only by the name itself, not by any stated behavior.

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 when-to-use guidance at all: nothing says whether this edits an existing custom notification versus creating one (that is notification-createCustom), and no prerequisites or conditions are given. The agent must infer usage entirely from the name.

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