Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-remove

Destructive

Removes a Dokploy notification by its notification ID, letting you clear specific alerts from the notification list.

Instructions

POST /notification.remove

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

Input Schema

NameRequiredDescriptionDefault
notificationIdYes

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 already declare destructiveHint=true and openWorldHint=true, so the safety profile is nominally covered, but the description adds nothing: it does not say whether the removal is permanent, whether it can fail if the notification is unread, or what the caller gets back. A bare route string carries no behavioral context for a destructive operation.

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 short, but that shortness reflects under-specification rather than economy. The single route string is not front-loaded with meaning because there is essentially no content to front-load.

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 destructive single-parameter mutation with no output schema and no annotation explanation, the description should explain the effect and irreversibility. It supplies none of that, leaving the definition incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter with 0% schema description coverage, so the description bears full responsibility for explaining 'notificationId' and does not. The parameter name is largely self-explanatory, which prevents a score of 1, but no format, source, or constraint guidance is given.

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 route string ('POST /notification.remove'), which restates the tool name rather than stating in plain language what the tool does. An agent can infer deletion of a notification by ID, but nothing is stated about the resource being a notification object, its scope, or the outcome.

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 conditions, no prerequisites, and no differentiation from the many sibling *-remove tools. The agent must guess entirely from the name and route.

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