Wraps Email for Amazon SES
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | No | The AWS region to use for SES. | |
| AWS_PROFILE | No | The AWS profile to use for credentials. | |
| WRAPS_WRITE_ENABLED | No | Set 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailA | Send a transactional email via your AWS SES account. Requires WRAPS_WRITE_ENABLED=true. The |
| list_recent_sendsA | List recently sent emails from your Wraps email history, newest first, at most |
| 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 |
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
With 7 tools covering send, monitor, diagnose, and plan, the surface is appropriately scoped for an email service without redundancy or bloat.
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.