Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createTelegram

Create a Telegram notification channel for Dokploy to send alerts about app deployments, build errors, backups, Docker cleanup, restarts, and server thresholds.

Instructions

POST /notification.createTelegram

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>",
      "botToken": "<botToken>",
      "chatId": "<chatId>",
      "messageThreadId": "<messageThreadId>"
    },
    "name": "notification-createTelegram"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
chatIdYes
botTokenYes
appDeployYes
volumeBackupYes
appBuildErrorYes
dockerCleanupYes
dokployBackupYes
databaseBackupYes
dokployRestartYes
messageThreadIdYes
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?

Annotations provide only openWorldHint=true and a title, so the description carries the full disclosure burden and delivers nothing. It does not say whether this persists a channel config, fires an outbound request, validates botToken/chatId, or what happens on duplicate names — notable gaps for a write tool with an external network hint.

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 very short and front-loaded by default, but the brevity comes from under-specification rather than efficiency — an endpoint path earns no place as the sole content of a description. There is no structure, no sentence of actual prose.

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-required-parameter mutation tool with no output schema and minimal annotations, the description is completely inadequate. None of the setup-critical details (credential requirements, event-flag semantics, effect of creation) are covered anywhere the agent can see.

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 12 required parameters, and the description adds no meaning for any of them. In particular the boolean event flags (appDeploy, dokployBackup, serverThreshold, etc.) and messageThreadId are completely unexplained, leaving the agent with bare names and no notion of accepted values or semantics.

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 REST route 'POST /notification.createTelegram', which essentially restates the tool name rather than describing what the tool does. An agent can infer a Telegram notification record is created, but the description supplies no verb+resource framing of its own and no differentiation from notification-updateTelegram or notification-testTelegramConnection.

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 mention of prerequisites, and no reference to the obvious siblings such as notification-testTelegramConnection (to verify credentials) or notification-updateTelegram (to modify an existing channel). An agent must guess the intended scenario entirely.

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