ClaudePost
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMTP_PORT | Yes | SMTP server port | |
| IMAP_SERVER | Yes | IMAP server address | |
| SMTP_SERVER | Yes | SMTP server address | |
| EMAIL_ADDRESS | Yes | Your email address | |
| EMAIL_PASSWORD | Yes | Your email password (app-specific password for Gmail) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-emailsC | Search emails within a date range and/or with specific keywords |
| get-email-contentB | Get the full content of a specific email by its ID |
| count-daily-emailsB | Count emails received for each day in a date range |
| send-emailA | CONFIRMATION STEP: Actually send the email after user confirms the details. Before calling this, first show the email details to the user for confirmation. Required fields: recipients (to), subject, and content. Optional: CC recipients. |
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 4 tools
Each tool has a clearly distinct purpose: count-daily-emails is for analytics, get-email-content retrieves specific emails, search-emails finds emails based on criteria, and send-email handles email sending with a confirmation step. 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 hyphens (e.g., count-daily-emails, get-email-content, search-emails, send-email). This predictable naming scheme enhances readability and reduces confusion for agents.
With 4 tools, the server is well-scoped for email management, covering key operations like counting, retrieving, searching, and sending emails. Each tool earns its place without feeling too sparse or bloated for the domain.
The tool set provides strong coverage for core email workflows, including read operations (count, get, search) and send functionality. A minor gap exists in update or delete operations for emails, but agents can still handle most common tasks effectively.