Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testDiscordConnection

Idempotent

Tests a Discord webhook connection to verify notifications will reach your channel. Send the webhook URL to confirm it works before configuring Dokploy alerts.

Instructions

POST /notification.testDiscordConnection

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": {
      "webhookUrl": "<webhookUrl>"
    },
    "name": "notification-testDiscordConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
decorationNo
webhookUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior3/5

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

Annotations declare openWorldHint=true and idempotentHint=true, which tells the agent this makes an external call and repeated calls are safe. The description, however, only gives the HTTP route; it does not say whether a message is actually posted to the channel, what auth or permissions are required, or how failures are surfaced. Given the annotation coverage, a 3 is a fair score, and there is no contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short and front-loaded, but it consists of a single route string that is not self-explanatory. Being concise earns credit for avoiding padding, but the brevity comes at the cost of any real explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter connectivity test with annotations covering safety and idempotency, the definition is borderline adequate, but with 0% schema description coverage and no explanation of the webhook URL or decoration flag, an agent cannot fully know what it is sending or what response to expect.

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?

Schema description coverage is 0%, so both parameters are documented only by type and constraints (webhookUrl is a required non-empty string, decoration is an optional boolean). The description does not explain that webhookUrl is a Discord webhook endpoint or what decoration toggles, so it does not compensate for the coverage gap.

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.testDiscordConnection', which restates the tool name rather than explaining in plain language that it sends a test message to a Discord webhook to verify configuration. An agent can infer the purpose from the name and route, but the description itself adds no verb-plus-resource statement.

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?

No when-to-use guidance is given, and no distinction from siblings such as notification-testSlackConnection or notification-createDiscord is made. The name implies a connectivity test, but the description neither states that nor rules out using it for actual notifications.

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