Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testCustomConnection

Idempotent

Tests a notification connection by sending a request to the specified endpoint with optional headers, helping verify notification delivery configuration.

Instructions

POST /notification.testCustomConnection

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": {
      "endpoint": "<endpoint>"
    },
    "name": "notification-testCustomConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
headersNo
endpointYes

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 already declare openWorldHint=true and idempotentHint=true, so the bar is lower, yet the description adds nothing beyond the route. It does not disclose that this likely sends a real outbound HTTP request to a user-supplied endpoint, what payload is delivered, whether failures are reported as errors, or any auth/rate-limit behavior — the very context an agent needs before triggering an external call.

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 and front-loaded, but only because it says almost nothing; this is under-specification rather than conciseness. A single route string is not a useful structure for an agent-facing tool description.

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 tool with a required free-form endpoint, a nested headers object, no output schema, and external side effects, the definition is wholly inadequate. An agent cannot tell what a successful test means, what is returned, or what happens on failure.

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 two parameters, including a nested free-form 'headers' object, so the description must compensate and does not. It never explains what 'endpoint' should contain (full URL? base URL? scheme requirements?) or how 'headers' are applied to the test request.

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 raw route string "POST /notification.testCustomConnection", which effectively restates the tool name plus an HTTP verb. It never states in plain language that this tests a custom notification connection (presumably by delivering a test payload), nor how that differs from the many sibling test tools such as notification-testDiscordConnection or notification-testSlackConnection.

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 prerequisites (e.g., the custom endpoint must already exist via notification-createCustom), and no exclusions or alternatives. The sibling set is full of near-identical testConnection tools, and the definition offers nothing to help an agent choose among them.

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