Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateDiscord

Idempotent

Updates an existing Discord notification configuration in Dokploy, including webhook URL and alert toggles for deployments, backups, server thresholds, and cleanup events.

Instructions

POST /notification.updateDiscord

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>",
      "discordId": "<discordId>"
    },
    "name": "notification-updateDiscord"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
appDeployNo
discordIdYes
decorationNo
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.8/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, and the description adds nothing beyond the HTTP method, so it does not contradict but also does not illuminate. It says nothing about which fields are overwritten versus left untouched, whether the target notificationId must exist, or what external Discord state (openWorld) is touched.

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 text is short, but its brevity comes from having almost no content rather than from efficient editing. A bare route string is not front-loaded information an agent can act on.

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?

This is a 14-parameter, two-required-field mutation tool with no output schema, no field documentation, and no annotation or description covering permissions or side effects. Given that complexity, a route string is wholly inadequate for an agent to invoke 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, so the schema provides no meaning and the description compensates with nothing. Critical fields such as webhookUrl, discordId, organizationId, and the eleven boolean event toggles 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 string "POST /notification.updateDiscord", which restates the tool name rather than explaining what the operation does. It implies an update of a Discord notification configuration, but never states what is being updated or what the result is.

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 at all, despite many near-identical siblings (notification-createDiscord, notification-testDiscordConnection, notification-updateSlack, etc.) that an agent must choose among. The only implicit signal is 'update' versus 'create' in the name, which the description does not reinforce.

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