Skip to main content
Glama
wraps-team

Wraps Email for Amazon SES

by wraps-team

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AWS_REGIONNoThe AWS region to use for SES.
AWS_PROFILENoThe AWS profile to use for credentials.
WRAPS_WRITE_ENABLEDNoSet to 'true' to enable the send_email tool. Defaults to false.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_emailA

Send a transactional email via your AWS SES account. Requires WRAPS_WRITE_ENABLED=true. The from address must be a verified Wraps domain. The to field accepts a single address or an array of addresses.

list_recent_sendsA

List recently sent emails from your Wraps email history, newest first, at most limit messages. The timestamp shown is the send time and is stable across calls. Returns send status, subject, recipient, timestamp, and messageId for each send. Use the messageId with get_email_event_log for full delivery details. The since parameter accepts a full ISO 8601 datetime string (e.g., 2024-01-01T00:00:00Z).

get_email_event_logA

Get the full delivery event log for a specific email by its messageId. Returns all SES events: Send, Delivery, Bounce, Complaint, Open, Click.

verify_domain_statusA

Check the verification and DKIM status of a sending domain in your AWS SES account. Returns whether the domain is verified for sending and its DKIM configuration status.

list_suppressionsA

List addresses on your AWS SES account-level suppression list, or check a single address with email. SES silently drops mail to suppressed addresses, and sending to them damages your sending reputation, so check before sending to an address you have not sent to recently. To determine whether one specific address is suppressed, always pass email — that is an exact lookup. The listing is paginated and states explicitly when it is truncated; a truncated listing is never proof that an address is unsuppressed. Optionally filter the listing by reason (BOUNCE or COMPLAINT).

get_setup_statusA

Check this AWS SES account's sandbox status and get a recommended next action for getting a first send out. Read-only — makes no changes to your AWS account.

estimate_costA

Estimate the monthly cost of sending email with Wraps + AWS: the Wraps platform fee, tracked-event overage, and an itemized AWS bill (SES, EventBridge, SQS, Lambda, DynamoDB, dedicated IP, WAF). Use this instead of calculating by hand — the cost model has several interacting variables, including which SES pricing plan the AWS account is on. Requires no AWS credentials.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool addresses a distinct aspect: sending, listing sends, retrieving event logs, checking domain verification, checking suppression list, checking setup status, and estimating cost. No two tools overlap in purpose, making selection unambiguous.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (send_email, list_recent_sends, get_email_event_log, verify_domain_status, list_suppressions, get_setup_status, estimate_cost). This predictability aids agent routing.

Tool Count5/5

With 7 tools covering send, monitor, diagnose, and plan, the surface is appropriately scoped for an email service without redundancy or bloat.

Completeness5/5

The set covers the core workflow: send, verify identity, check suppression, observe delivery events, and estimate cost. Missing administrative operations (e.g., adding domains) are reasonable omissions given the server's focus on sending and observability.

Maintenance

ActivityActive
ResponsivenessNo issues