Email-MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_email_sendD | 发送邮件 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose of sending emails.
The naming is trivially consistent as there is only one tool. The tool name 'mcp_email_send' follows a clear pattern with a prefix, resource, and verb, though consistency cannot be assessed across multiple tools.
A single tool for an email server is too few for the apparent scope. Email management typically requires operations like reading, listing, deleting, or searching emails, making this set feel incomplete and thin.
The tool set is severely incomplete for an email domain. It only provides a send function, lacking essential operations such as receiving, reading, listing, or managing emails, which will cause significant agent failures in handling email-related tasks.