GoodSender

Send Pending Emails

send_pending_emails

Destructive

Send queued custom and template emails whose recipients have granted consent since they were queued.

Refreshes sender domains and recipient consent state from GoodSender, then hands every queued email whose recipient has now consented to the mail queue, which sends it within seconds. Sending cannot be undone. Emails whose recipient has not consented stay queued; emails to recipients who declined are dropped. Returns the remaining queue per sender domain.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send_pending_emails"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`EmailsPerDomain`	Yes	Queued email per sender domain after the refresh. Key is the domain.
`ConsentStateAsOf`	Yes	When recipient consent state was refreshed from GoodSender by this call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: sender domains and consent state are refreshed from GoodSender, sending is irreversible, non-consented emails stay queued, and declined recipients are dropped. It does not cover auth or rate-limit details, but the annotations already establish the destructive and non-idempotent profile.

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

Conciseness4/5

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

The description is front-loaded and dense, with no wasted background. The final sentence about returning the remaining queue is somewhat redundant because an output schema exists, but it is brief and not disruptive.

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

Completeness5/5

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

Given the zero-parameter schema, the rich annotations, and the presence of an output schema, the description is complete enough for an agent to invoke the tool correctly. It explains consent gating, irreversible sending, and queue handling.

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

Parameters4/5

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

This tool has zero parameters, so there are no parameter semantics to explain. The baseline for a zero-parameter schema is 4.

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 states a precise verb and resource: sending queued custom and template emails whose recipients have granted consent since queuing. It also distinguishes the behavior from a generic send by explaining the consent-gated queue semantics.

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

Usage Guidelines4/5

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

It clearly explains the conditions under which emails are sent, remain queued, or are dropped. However, it does not explicitly compare this tool against alternatives such as enqueue_email, enqueue_template_email, or send_consentless_email.

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

All GoodSender tools Inspect

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.