blastengine-mailer
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 |
|---|---|
| send_emailC | Send an email using Blastengine API |
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 'send_email' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The naming is trivially consistent as there is only one tool, 'send_email', which follows a clear verb_noun pattern. There are no other tools to compare against, so no inconsistency can exist.
A single tool is too few for a mailer server's apparent scope, which typically involves operations like listing emails, managing templates, or checking statuses. This minimal set limits functionality and may cause agent failures due to lack of essential operations.
The tool surface is severely incomplete for an email service domain. While 'send_email' covers a core action, there are significant gaps such as retrieving sent emails, managing recipients, handling attachments, or error checking, which are essential for comprehensive email workflows.