Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-receiveNotification

Idempotent

Receive CPU or memory threshold alert notifications from Dokploy or remote servers, including values, messages, timestamps, and authentication tokens.

Instructions

POST /notification.receiveNotification

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": {
      "Type": "<Type>",
      "Value": "<Value>",
      "Threshold": "<Threshold>",
      "Message": "<Message>",
      "Timestamp": "<Timestamp>",
      "Token": "<Token>"
    },
    "name": "notification-receiveNotification"
  }
}

Input Schema

NameRequiredDescriptionDefault
TypeYes
TokenYes
ValueYes
MessageYes
ThresholdYes
TimestampYes
ServerTypeNoDokploy

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 supply only openWorldHint=true and idempotentHint=true, leaving destructive/read semantics and side effects unstated, and the description adds nothing beyond a route string. It does not disclose that a Token is required for authorization, what happens on threshold breach, or what the call returns for a mutation-flavored POST.

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 only because it is under-specified rather than efficient; a bare route string conveys no information an agent can act on. There is no front-loaded purpose statement to anchor the rest.

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 seven-parameter tool with no schema descriptions, no output schema, and thin annotations, the description should carry nearly the full explanatory burden. It carries none, so an agent cannot invoke this correctly without opening the raw schema.

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 seven parameters with six required, and the description contributes no parameter meaning at all. Critical fields like Token, Threshold, Type and ServerType are left entirely undocumented, including whether Token is an auth credential or an output routing key.

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 HTTP route 'POST /notification.receiveNotification', which restates the tool name rather than explaining what the operation does. It does not say whether this accepts an incoming alert, creates a notification record, or forwards to configured channels, and it gives no basis for distinguishing it from the many notification-* siblings.

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 call this tool, when not to, or how it relates to siblings such as notification-createCustom or notification-testCustomConnection. An agent must guess from the 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