DoubleTick MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_tracked_emailA | Send an email with read tracking via Gmail. Body accepts markdown (converted to HTML automatically). The email is sent immediately via Gmail API. |
| check_tracking_statusA | Check if a tracked email has been opened. Returns open count, device info, and timestamps. |
| list_tracked_emailsC | List recent tracked emails with their open status. |
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 3 tools
Each tool has a clearly distinct purpose: check_tracking_status focuses on detailed status of a specific tracked email, list_tracked_emails provides a summary list of recent emails, and send_tracked_email handles sending new emails. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern with snake_case (check_tracking_status, list_tracked_emails, send_tracked_email). The naming is predictable and readable, with no deviations in style or convention.
With 3 tools, the server is well-scoped for email tracking via Gmail, covering core operations: sending, listing, and checking status. It feels slightly thin but reasonable, as it handles the essential workflow without unnecessary complexity.
The tool set covers the main email tracking lifecycle: send, list, and check status. A minor gap exists in operations like deleting or updating tracked emails, but agents can work around this, and the core functionality is adequately covered for the domain.