Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createResend

Configure Resend email alerts for Dokploy events by defining the API key, sender and recipient addresses, and notification triggers.

Instructions

POST /notification.createResend

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": {
      "appBuildError": "<appBuildError>",
      "databaseBackup": "<databaseBackup>",
      "dokployBackup": "<dokployBackup>",
      "volumeBackup": "<volumeBackup>",
      "dokployRestart": "<dokployRestart>",
      "name": "<name>",
      "appDeploy": "<appDeploy>",
      "dockerCleanup": "<dockerCleanup>",
      "serverThreshold": "<serverThreshold>",
      "apiKey": "<apiKey>",
      "fromAddress": "<fromAddress>",
      "toAddresses": "<toAddresses>"
    },
    "name": "notification-createResend"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
apiKeyYes
appDeployYes
fromAddressYes
toAddressesYes
volumeBackupYes
appBuildErrorYes
dockerCleanupYes
dokployBackupYes
databaseBackupYes
dokployRestartYes
serverThresholdYes

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?

The only annotation is openWorldHint=true, which conveys nothing about side effects. The description does not disclose that this performs a write/persistent creation, whether an API key from Resend is required, whether the call validates credentials, or what happens on duplicate names.

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 shortness here is under-specification rather than conciseness — a bare route string with no front-loaded purpose statement. Nothing in it earns its place as a description.

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 12-parameter, all-required mutation tool with no output schema, the definition supplies no behavioral, parameter, or usage context whatsoever. It is completely inadequate for the tool's complexity.

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?

Twelve required parameters at 0% schema description coverage, and the description adds no meaning for any of them. An agent cannot tell from the definition what 'serverThreshold', 'dockerCleanup', or the boolean flags actually toggle, nor what fromAddress/toAddresses require.

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.createResend', which restates the tool name rather than explaining what the tool does. It never says this creates a Resend email notification channel, nor how that differs from siblings like notification-updateResend or notification-createEmail.

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 zero guidance on when to use this versus the many sibling creation tools (createEmail, createSlack, etc.) or versus the update variant. An agent has to infer everything from the tool 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