Skip to main content
Glama

Connections

by icu.connections
OverviewDiscussionsAdmin

Send an email from the member's own domain

connections_email_send

Use this when the member asks to send or email someone from their own business domain (Connections Send). Sends ONE real message, now or at a scheduled time; it lands in the recipient's inbox and cannot be recalled, and dry_run:true returns the exact message without sending it. The sender must be on a domain this workspace has connected and verified. When nothing goes out, the reply is an error naming why: a suppressed recipient, an unverified domain, a spent daily ceiling, or no credits. To check on a sent message use connections_email_get; to see what went out use connections_emails_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoOptional carbon-copy recipients.
toYesOne recipient address, or several.
bccNoOptional blind-copy recipients.
fromYesThe sender, on a domain this workspace has connected and verified. May be 'Name <you@yours.com>'.
htmlNoThe HTML body. Not with `template`.
textNoThe plain-text body. Send text, html, or both. Not with `template`.
dry_runNotrue previews the exact call with nothing sent.
subjectNoThe subject line. Required unless `template` names a stored template that carries one.
reply_toNoWhere replies should go, when that is not the sender.
templateNoThe name of a template stored in this workspace (e.g. 'order-receipt'), used INSTEAD of text/html. Its placeholder values go in `variables`.
variablesNoValues for the template's {{placeholders}}, as a flat object. Every placeholder needs one.
scheduled_atNoOptional send time: an ISO instant WITH a timezone ('2026-10-01T09:00:00Z') or a relative time ('in 2 hours'). A time with no timezone returns an error asking for the zone. Omit to send now.
idempotency_keyNoYour own key for this message. Sending the same key twice returns the first result instead of sending again - set it whenever a retry is possible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavioral traits: the message is irreversible ('cannot be recalled'), dry_run:true prevents sending, the sender must be on a verified connected domain, and failure returns named error reasons (suppressed recipient, unverified domain, daily ceiling, credits). This is rich behavioral context that the sparse annotations do not provide.

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 compact but information-dense: trigger, core behavior, irreversibility, dry-run, domain prerequisite, error behavior, and sibling routing are all present in five sentences. It is front-loaded with the use case and contains no redundant filler.

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

Completeness4/5

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

For a complex 13-parameter send tool with no output schema, the description covers purpose, usage, prerequites, failure behavior, and sibling tools. The only notable gap is that it does not describe the success response shape (e.g., message ID), which would be useful since there is no output schema to rely on.

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?

Schema description coverage is 100%, so the schema already documents all 13 parameters. The description adds no parameter-specific meaning beyond the schema, only general send behavior. This matches the baseline 3 for full schema coverage.

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

Purpose5/5

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

The description opens with a specific use case ('when the member asks to send or email someone from their own business domain') and names the tool's action as sending ONE real message. It also differentiates from siblings by pointing to connections_email_get and connections_emails_list for follow-up tasks.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool ('Use this when the member asks to send...') and provides sibling alternatives for related tasks ('To check on a sent message use connections_email_get; to see what went out use connections_emails_list'). This gives the agent clear routing guidance.

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

All Connections toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources