Skip to main content
Glama

create_email_message_by_user_id

Idempotent

Create and send personalized email messages to specific users by their ID within the Eduframe platform, using customizable templates with dynamic tags.

Instructions

Create and send an email message to a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesID of the email
fromYesFrom field of the email. The default is the educator reply to email. It is possible to use tags delimited by two pairs of curly braces, i.e. `{{educator.reply_to}}`.
subjectYesSubject line of the email. It is possible to use tags delimited by two pairs of curly braces, i.e. `{{user.full_name}}`.
bodyYesBody field of the email, allowing HTML format. It is possible to use tags delimited by two pairs of curly braces, i.e. `{{user.full_name}}`. Since this is JSON it does not accept `"` characters and multi-line strings. The body must be properly escaped before sending. This can be done automatically or manually. Example tool: https://www.freeformatter.com/json-escape.html#before-output
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description confirms the dual action of creating and sending (not just drafting), which complements the annotations (readOnlyHint: false). However, it fails to elaborate on the idempotentHint: true annotation (what makes resending safe), nor does it mention delivery guarantees, rate limits, or failure behaviors that would help an agent understand operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence of nine words with no filler. It immediately communicates the core action without preamble, making it appropriately front-loaded for quick agent comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple 4-parameter schema with complete field documentation and no output schema, the description is minimally adequate. However, for an email-sending operation, it lacks context about return values (confirmation IDs, success indicators) or side effects (notification triggers, audit logging), which would be valuable given the operation's importance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline score applies. The schema comprehensively documents all four parameters including template syntax (curly braces) and JSON escaping requirements for the body field. The description adds no parameter-specific guidance, so it meets but does not exceed the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates and sends an email message to a user, using specific verbs ('Create and send') and identifying the resource (email message). It aligns with the tool name's implication of targeting a specific user, though it could explicitly mention the user_id parameter to fully distinguish it from potential bulk email tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., user existence verification), or when not to use it. It does not mention if this is for transactional emails only or marketing emails, nor does it reference the sibling tools that might handle email-related tasks differently.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/martijnpieters/eduframe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server