DingusMail
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_emlA | Parse an .eml file and return metadata, content, and attachment info. Does NOT extract attachment bytes - use extract_eml_attachments for that. Perfect for previewing what's in an email without bloat. |
| extract_eml_attachmentsA | Extract attachments from .eml file with smart organization. Organizes files into folders:
|
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 2 tools
The two tools have clearly distinct purposes: parse_eml provides a preview of email content and metadata, while extract_eml_attachments focuses solely on extracting attachment files. There is no overlap; the tool descriptions explicitly cross-reference each other to avoid confusion.
Both tool names follow a consistent verb_noun pattern with snake_case: parse_eml and extract_eml_attachments. The verbs 'parse' and 'extract' accurately describe the operations, and the nouns clearly identify the target resources.
With only two tools, the server feels thin even for a narrow domain like .eml handling. While each tool is valuable, the count is borderline and might warrant additional tools for a more complete workflow.
The two tools cover the primary read-oriented operations for .eml files: inspecting content and extracting attachments. Minor gaps exist, such as no ability to modify or create .eml files, but for the apparent purpose of parsing and extraction, the surface is reasonably complete.