Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateGotify

Idempotent

Updates a Gotify notification configuration in Dokploy using its notification and Gotify IDs, letting you adjust app token, server URL, priority, and alert event triggers.

Instructions

POST /notification.updateGotify

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>",
      "gotifyId": "<gotifyId>"
    },
    "name": "notification-updateGotify"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
appTokenNo
gotifyIdYes
priorityNo
appDeployNo
serverUrlNo
decorationNo
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
notificationIdYes
organizationIdNo
serverThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare openWorldHint=true and idempotentHint=true, but the description adds no behavioral context whatsoever. Critically, it does not say whether this is a partial patch or a full replace of the Gotify notification (i.e. whether omitted fields are cleared), nor whether auth or ownership checks apply for the required notificationId/organizationId. For a 16-parameter mutation endpoint, that silence is a serious 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?

The single line is not bloated, but it is not concise in any useful sense — it is under-specified to the point of carrying no information beyond the name. There is no front-loaded statement of intent to build 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?

Given 16 undocumented parameters, no output schema, and annotations that only cover openness and idempotency, the definition leaves an agent without the information needed to construct a correct call. It should at minimum state the update semantics, the meaning of required identifiers, and the event-flag booleans.

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, so the description carries the full burden of explaining them and explains none. Fields like appToken, serverUrl, priority, decoration, and the many boolean event flags (appDeploy, databaseBackup, dockerCleanup, etc.) have no stated meaning, and the description does not even note that notificationId/gotifyId are required. An agent cannot distinguish an event subscription flag from a display option.

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.updateGotify", which restates the tool name rather than defining it. It implies an update of a Gotify notification configuration, but gives no statement of what is actually updated or what the tool returns. An agent must infer everything from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 alternatives such as notification-createGotify or notification-testGotifyConnection, and no prerequisites. The only implicit signal is the verb "update", which the name already carries.

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