Skip to main content
Glama
Sign In
@kieksme/listmonk-mcp

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Test SMTP Settings

listmonk_test_smtp_settings
Read-onlyIdempotent

Tests an SMTP server configuration by sending a test email without saving it, so you can verify connectivity before applying settings.

Instructions

Tests connectivity to an SMTP server configuration without saving it, by sending a test e-mail.

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": {
      "email": "<email>",
      "smtp_settings": "<smtp_settings>"
    },
    "name": "listmonk_test_smtp_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesRecipient address that the SMTP test message will be sent to.
smtp_settingsYesThe SMTP server block to test — fields like host, port, auth_protocol, username, password, tls_type (see the 'smtp' array entries from listmonk_get_settings for the expected shape). This tests connectivity WITHOUT saving the settings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond those annotations: a real e-mail is dispatched to the recipient and the submitted block is discarded rather than persisted, which an agent should know before invoking it repeatedly.

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

Conciseness5/5

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

A single front-loaded sentence with the action, the mechanism (sending a test e-mail) and the crucial non-persistence constraint. No redundant or filler wording.

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

Completeness4/5

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

With only two fully documented required parameters and no output schema, the definition covers what an agent needs to call it correctly. The only omission is any hint about the shape of the result (e.g., success/failure or error detail from the SMTP handshake).

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

Parameters3/5

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

Schema description coverage is 100%, and the smtp_settings property already documents host/port/auth_protocol/username/password/tls_type and points at listmonk_get_settings for the expected shape. The description adds nothing about parameter formats or defaults beyond what the schema states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — testing SMTP connectivity by sending a test e-mail — and adds the key qualifier that settings are not saved. This clearly separates it from siblings like listmonk_update_settings and listmonk_get_settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'without saving it' implies the intended use case (validating credentials before persisting them), but the description never states when to call this versus alternatives such as listmonk_update_settings or listmonk_send_transactional_message. Usage is inferable rather than stated.

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