Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateResend

Idempotent

Updates a Dokploy Resend notification configuration, including API key, sender and recipient addresses, and event toggles for deployment, backup, and server alerts.

Instructions

POST /notification.updateResend

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>",
      "resendId": "<resendId>"
    },
    "name": "notification-updateResend"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
apiKeyNo
resendIdYes
appDeployNo
fromAddressNo
toAddressesNo
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 supply only openWorldHint=true and idempotentHint=true, leaving the mutation profile undisclosed. The description adds nothing: it does not say whether this is a partial or full replacement update, what happens to omitted fields, whether credentials (apiKey) are validated on write, or whether changes affect live alerting immediately. For a write tool with no readOnly/destructive hints, this is a major gap.

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 a single short string with no wasted words, but that brevity is under-specification rather than conciseness. There is no front-loaded statement of intent, just an 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 no parameter descriptions, the definition is essentially empty. The agent cannot determine update semantics, field meanings, or side effects from what is provided.

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 description must compensate and instead provides zero information. Critical ambiguities go unaddressed, such as which boolean flags (appDeploy, dockerCleanup, databaseBackup, serverThreshold, etc.) are being toggled, what apiKey/fromAddress/toAddresses mean in the update context, and why organizationId is optional while notificationId and resendId are required.

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.updateResend', which restates the tool name rather than stating what the tool does in agent terms. An agent can guess it updates a Resend notification configuration, but the description itself never says 'update the Resend email notification settings' or distinguishes it from the sibling notification-updateEmail or notification-createResend.

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, no prerequisites, and no mention of alternatives such as notification-createResend or notification-testResendConnection. The agent is left to infer everything from the name alone.

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