Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateNtfy

Idempotent

Update an existing Ntfy notification configuration in Dokploy, including topic, server URL, access token, priority, and alert event toggles.

Instructions

POST /notification.updateNtfy

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>",
      "ntfyId": "<ntfyId>"
    },
    "name": "notification-updateNtfy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
topicNo
ntfyIdYes
priorityNo
appDeployNo
serverUrlNo
accessTokenNo
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 only declare idempotentHint=true and openWorldHint=true; the description adds nothing about permissions, what fields get overwritten, whether unspecified fields revert, or how errors surface. For a 16-parameter mutation endpoint, a bare route string leaves the entire behavioral burden uncovered.

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 trivially short with no wasted words, but that is under-specification rather than conciseness. The single route fragment carries no front-loaded purpose statement an agent could 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?

A 16-parameter mutation endpoint with no output schema and minimal annotations requires a real description, and this one offers none. Nothing tells the agent which parameters are meaningful, what the required notificationId/ntfyId do, or what a successful response looks like.

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 16 parameters, and the description compensates for none of it. Names like serverThreshold, volumeBackup, or priority have no explanation anywhere, so an agent cannot know which event toggles or credentials are relevant.

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 route string "POST /notification.updateNtfy", which essentially restates the tool name rather than describing what the operation does. It implies an update to an ntfy notification but gives no verb-and-resource phrasing or scope, and does nothing to separate it from siblings like notification-createNtfy or notification-updateCustom.

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 guidance on when to use this tool, when not to, or which sibling to pick instead. An agent must guess that this modifies an existing ntfy notification rather than creating a new one or testing a connection, all of which exist in the sibling list.

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