Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updatePushover

Idempotent

Updates a Dokploy Pushover notification configuration, adjusting API credentials, priority, retry/expiry, and event toggles.

Instructions

POST /notification.updatePushover

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>",
      "pushoverId": "<pushoverId>"
    },
    "name": "notification-updatePushover"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
retryNo
expireNo
userKeyNo
apiTokenNo
priorityNo
appDeployNo
pushoverIdYes
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
notificationIdYes
organizationIdNo
serverThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already state openWorldHint=true and idempotentHint=true, but the description adds nothing beyond them — it does not say what is mutated, whether omitted fields are preserved or cleared, whether apiToken/userKey must be re-supplied, or what happens on an invalid notificationId. It does not contradict the annotations, it simply contributes no behavioral context for a 17-parameter mutation.

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 short, but it is under-specified rather than concise — it spends its only content restating the HTTP route instead of front-loading purpose or requirements. Brevity here comes at the cost of all useful information.

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 17-parameter mutation with no output schema and no schema descriptions, the definition is completely inadequate; an agent cannot know which fields are required, what the numeric bounds mean, or what a successful update returns. Nothing compensates for the missing schema documentation.

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 17 parameters, so the description carries the full burden and delivers none of it. Key semantics such as priority (-2 to 2 meaning), retry/expire interaction, the minLength constraints, and which event flags control what are entirely undocumented.

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 an HTTP method and route, 'POST /notification.updatePushover', which restates the tool name rather than stating what the tool does. An agent can infer it updates a Pushover notification config, but nothing is said about what gets updated or what effect that has, and no sibling (e.g. createPushover, testPushoverConnection) is distinguished from it.

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 at all — no mention of when to update versus create a Pushover target, no prerequisites (e.g. needing an existing notificationId), and no conditions or exclusions. The agent must 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