Skip to main content
Glama
Sign In

Mailercloud

by io.github.mailercloud-com
OverviewDiscussionsAdmin

Add Sender

add_sender

Add a sender (the From name and address on campaigns). The address must be on a sending domain that is already verified (see list_domains); otherwise Mailercloud refuses it. Needs sender_email and sender_name. Set dry_run: true to validate without adding.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sender_email": "<sender_email>",
      "sender_name": "<sender_name>"
    },
    "name": "add_sender"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoValidate and show what would be added without adding anything
sender_nameYesSender display name shown to recipients, e.g. your business name
sender_emailYesSender email address on a verified sending domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly=false, destructive=false, openWorld=true), and the description adds real behavior: server-side rejection when the domain isn't verified and a side-effect-free dry_run mode. It omits what happens if the sender already exists (relevant since idempotentHint is false) and what the call returns.

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?

Three short sentences, front-loaded with the definition, then the constraint, then the safe-preview option. No filler or repetition beyond the required-parameter note.

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 3-parameter mutation tool with no output schema and no nested objects, the description covers identity, prerequisite, failure mode, and a validation path. The only gap is undisclosed return content or duplicate-sender handling.

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 coverage is 100%, so all three parameters are already documented in structured form. The description only restates that sender_email and sender_name are needed and repeats the dry_run meaning rather than adding format or constraint detail, so the baseline 3 applies.

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?

Names the specific verb and resource ('Add a sender') and immediately defines the concept in domain terms ('the From name and address on campaigns'), which disambiguates it from siblings like add_domain, list_senders, and delete_sender.

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?

Gives a concrete precondition (the address must sit on an already-verified sending domain) and points to list_domains as the tool for checking that, plus a dry_run path for pre-validation. It stops short of explicitly contrasting with add_domain or list_senders, but the routing guidance present is strong.

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

All Mailercloud 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