Skip to main content
Glama
ni-c

smtp-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check the SMTP connection

test_connection
Read-onlyIdempotent

Verifies SMTP connectivity and authentication by connecting, negotiating TLS, and authenticating without sending a message. Helps distinguish configuration issues from delivery failures; rate-limited to once per 10 seconds.

Instructions

Opens a connection to the SMTP server, negotiates TLS and authenticates, then closes it again. No message is sent. Use it to tell a configuration problem apart from a delivery problem. Tries the server at most once every ten seconds; a call inside that window repeats the previous outcome and says so.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tlsYes
hostYes
noteYes
portYes
cachedYesTrue when this repeats an attempt made within the last ten seconds.
reachableYes
authenticatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedOutput schema / properties / cached
      Added value: +{
+  "description": "True when this repeats an attempt made within the last ten seconds.",
+  "type": "boolean"
+}
    • changedOutput schema / required
      Previous value: -[
-  "reachable",
-  "host",
-  "port",
-  "tls",
-  "authenticated",
-  "note"
-]New value: +[
+  "reachable",
+  "host",
+  "port",
+  "tls",
+  "authenticated",
+  "cached",
+  "note"
+]
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses side effects (no message sent, connection closed), rate limiting (at most once every ten seconds), and idempotent caching (repeats previous outcome). This goes beyond the annotations and fully informs about behavior.

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?

The description is four sentences, each serving a distinct purpose: action, clarification of scope, use case, and rate limit. It is front-loaded and free of unnecessary detail.

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

Completeness5/5

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

The description covers the tool's operation, its diagnostic use case, and its rate-limiting behavior. With no parameters and an output schema present, the description provides all necessary context for correct use.

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

Parameters4/5

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

The tool has no parameters, so there is nothing to explain. The description does not add param-specific details, but the baseline for zero parameters is 4, and the description is otherwise clear.

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 action (opens connection, negotiates TLS, authenticates, closes) and explicitly distinguishes it from diagnosing delivery problems. It clearly identifies the tool's purpose.

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

Usage Guidelines5/5

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

It directly instructs when to use the tool ('tell a configuration problem apart from a delivery problem') and documents the rate limit and caching behavior, giving clear guidance on usage.

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