Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testEmailConnection

Idempotent

Tests SMTP email notification settings by sending a message to specified recipients, helping verify server, port, credentials, and sender details before enabling notifications.

Instructions

POST /notification.testEmailConnection

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": {
      "smtpServer": "<smtpServer>",
      "smtpPort": "<smtpPort>",
      "username": "<username>",
      "password": "<password>",
      "toAddresses": "<toAddresses>",
      "fromAddress": "<fromAddress>"
    },
    "name": "notification-testEmailConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
smtpPortYes
usernameYes
smtpServerYes
fromAddressYes
toAddressesYes

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 declare openWorldHint=true and idempotentHint=true, so the description's only added signal is the HTTP method/path. Critically, it never discloses the key side effect: this appears to actually deliver a test email to the supplied toAddresses using live SMTP credentials, which is essential for an agent to know before invoking. It also omits error/failure semantics for a bad connection.

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 a single short line with no wasted words, but that brevity is under-specification rather than conciseness. There is no front-loaded statement of intent, so the reader learns nothing actionable.

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 six required credential and addressing parameters, no output schema, and a real-world side effect (sending mail), this description is completely inadequate. Nothing about outcomes, credential handling, or failure behavior is provided.

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 six required parameters (smtpServer, smtpPort, username, password, toAddresses, fromAddress), and the description adds no meaning to any of them. Format expectations for smtpServer, port conventions, TLS/auth expectations, and whether multiple toAddresses are sent individually or together are all 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 a bare route restatement, "POST /notification.testEmailConnection", which essentially repeats the tool name in HTTP form. It conveys no more than that this is a POST endpoint related to testing an email connection; it does not say what the test does, what it connects to, or how it differs from the many sibling notification-test*Connection tools.

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 whatsoever — no prerequisites, no mention of needing a saved email config first, and no differentiation from siblings like notification-testCustomConnection or notification-testSlackConnection. An 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