Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateTelegram

Idempotent

Update an existing Telegram notification in Dokploy by setting its bot token, chat ID, and alert event toggles for deployment, backup, and server events.

Instructions

POST /notification.updateTelegram

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>",
      "telegramId": "<telegramId>"
    },
    "name": "notification-updateTelegram"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
chatIdNo
botTokenNo
appDeployNo
telegramIdYes
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
notificationIdYes
organizationIdNo
messageThreadIdNo
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 declare idempotentHint=true and openWorldHint=true, but the description adds nothing beyond that — no statement of which fields get modified, whether unnamed fields are preserved or cleared, or what credentials/permissions are needed for a 15-parameter mutation. With zero annotation coverage of mutation semantics, the description carries the full burden and fails to meet it; it neither contradicts nor supplements the annotations.

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 this is under-specification rather than conciseness: a single endpoint string with no structure, no front-loaded purpose statement, and no useful content to be concise about.

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 mutation tool with 15 parameters, 0% schema coverage, no output schema, and only sparse annotations, the description is wholly inadequate. An agent cannot determine required inputs, mutation semantics, or how this differs from the many sibling update tools.

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, only 2 of which are required (notificationId, telegramId). The description names no parameters and explains nothing about botToken, chatId, messageThreadId, or the various boolean event flags, leaving the agent with no semantic guidance for a large and ambiguous parameter surface.

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.updateTelegram", which restates the tool name and HTTP method rather than explaining in plain language what the tool does. An agent can infer that it updates a Telegram notification config, but no verb+resource articulation or scope is given, and there is no differentiation from sibling tools like notification-createTelegram or notification-updateSlack beyond the endpoint path itself.

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 when to prefer create vs update, no prerequisites (e.g. needing an existing notificationId), and no reference to alternatives such as notification-createTelegram or notification-testTelegramConnection. The agent must infer everything 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