Skip to main content
Glama

smtp_verify_account

Read-onlyIdempotent

Tests SMTP account connectivity and authentication to confirm email sending credentials work before use.

Instructions

Test SMTP account connectivity and authentication

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "smtp_verify_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAccount identifier (defaults to `"default"`)default

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description's main added value is distinguishing two separate checks (connectivity and authentication). It does not disclose what happens on failure (error vs. a false result), though an output schema exists.

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

Conciseness4/5

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

One short sentence with zero filler, front-loading the action. It is appropriately sized for a simple verification tool, though it could carry one more clause about prerequisites without bloat.

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 one-parameter, read-only verification tool with an output schema and full annotation coverage, the definition is nearly sufficient. It still omits whether credentials must be pre-configured and how success/failure is surfaced.

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 single account_id parameter is documented in the schema, including its default. The description adds no meaning about which account is targeted or how account_id is resolved, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb+resource: 'Test SMTP account connectivity and authentication.' An agent can distinguish it from imap_verify_account because the description names SMTP explicitly and clarifies the check covers both connectivity and auth. It stops short of explicitly contrasting with the IMAP sibling.

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 explicit when-to-use guidance, no prerequisites (e.g., credentials must already be configured), and no named alternatives. The implied use, validating an account before sending, is left for the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.