dead-letter
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_emlA | Convert a .eml email file to Markdown with YAML front matter. Returns the full Markdown content (front matter + body). When output_path is provided, also writes the file to disk. Attachments are listed in the front matter but not written to disk; use convert_eml_to_bundle to save the decoded attachment files. thread_mode="structured" adds a section per earlier reply or forwarded message. Gmail HTML forwards and unquoted plain-text forwards are kept in latest mode too; a plain-text forward inside ">" quoting is not. Presets bundle common flag combinations:
Individual flags override the preset when provided. |
| convert_eml_to_bundleB | Convert a .eml file to a self-contained bundle with markdown and attachments. Creates a directory containing the converted markdown, extracted attachments, and optionally the original .eml source. source_handling only accepts 'copy' over MCP: the original .eml is copied into the bundle and left untouched. The 'move' and 'delete' modes are rejected here — use the CLI or the Python API for those. Returns JSON with bundle_path, markdown_path, attachment_paths, and optional diagnostics. |
| convert_directoryA | Batch convert all .eml files in a directory to Markdown. Recursively finds .eml files (at most 50 per call; larger directories are rejected before any conversion). output_directory is required: Markdown is written there, mirroring subfolders, and source .eml files are left in place. Returns a JSON summary with total, successes, failures, output_paths, and errors. Use convert_eml to retrieve individual converted file content. |
| convert_mboxA | Convert one flat .mbox archive (e.g. Gmail Takeout) to Markdown files. Bounded: the archive must be at most 256 MiB, and conversion stops after 1000 messages (the response then has truncated=true; use the dead-letter CLI for larger archives). Compressed archives and Apple Mail .mbox directories are rejected. output_directory is required; one .md per message (or one bundle directory when bundles=true) is written there with a collision-safe JSON report. The source archive is never modified. Returns a JSON summary (processed, converted, skipped, failed, truncated, report_path, and at most 20 failure entries), never message content. Cancellation is not supported; the bounds limit call duration. |
| get_diagnosticsB | Inspect email quality and structure without writing permanent files. Use this to assess conversion quality before committing, or to troubleshoot problematic .eml files. Always returns JSON with: state (normal/degraded/review_recommended), selected_body, segmentation_path, client_hint, confidence, fallback_used, and warnings. Two keys are conditional: stripped_images appears only when images were removed, and attachments only when the message had attachments eligible for retention. |
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 5 tools
The tools are largely distinct: convert_eml, convert_directory, and convert_mbox differ by input source, and get_diagnostics is clearly separate. The only mild overlap is convert_eml vs convert_eml_to_bundle, but the descriptions make the boundary (markdown-only vs markdown+attachments on disk) clear.
Names follow a predictable verb_noun pattern with consistent snake_case: convert_eml, convert_eml_to_bundle, convert_directory, convert_mbox, and get_diagnostics. The verb prefixes (convert_, get_) are used consistently and readably.
Five tools is well-scoped for an email conversion server, with each tool covering a distinct input source (single .eml, .eml bundle, directory, .mbox) plus a diagnostics utility. No tool feels redundant or padded.
The surface covers the core conversion lifecycle across all expected input sources and offers diagnostics for quality assessment. Minor gaps exist: source_handling move/delete modes are CLI-only, and retrieving batch output content still requires convert_eml rather than a dedicated reader, but agents can work around these.