Skip to main content
Glama

agent-cold-email

by io.github.YS-projectcalc
OverviewDiscussionsAdmin

setup_infrastructure

Provision sending infra: buy lookalike domains, create mailboxes, start warmup. Inputs: brand, primaryDomain, domains + inboxesEach (or distribution), persona, physicalAddress, senderIdentity. Billing is per provisioned mailbox; quoteOnly:true previews cost first. domains/inboxesEach are the infra you want to HAVE, not an amount to add — a repeat call never buys twice; each ordinal 0..domains-1 fills to its own count. Mailbox addresses are DETERMINISTIC from persona+ordinal+slot — keep persona unchanged on a retry. registerDomains:true is required consent before any NEW domain purchase; omitting it on a buy call is refused 400 registrar_optin_missing (self-correct by resending true, never an operator escalation) — also needs registrant, unless already on file. NO background retry exists: a provisioning result (pending|capacity_pending) needs YOU to retry to progress; capacity_pending needs contact_operator instead. Returns { jobId, billing, provisioning?, nextSteps }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYes
domainsYes
personaYes
quoteOnlyNo
registrantNo
inboxesEachNo
distributionNo
primaryDomainYes
idempotencyKeyNoOptional idempotency key: resend the SAME key when retrying this call so a dropped-response retry is not applied twice (no duplicate campaign/provision/send).
senderIdentityYes
physicalAddressYes
registerDomainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / distribution
      Added value: +{
+  "items": {
+    "maximum": 10,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "brand",
-  "primaryDomain",
-  "domains",
-  "inboxesEach",
-  "persona",
-  "physicalAddress",
-  "senderIdentity"
-]New value: +[
+  "brand",
+  "primaryDomain",
+  "domains",
+  "persona",
+  "physicalAddress",
+  "senderIdentity"
+]
  2. Changed1 schema field changed
    • removedInput schema / properties / registerDomains / default
      Removed value: -false
  3. Changed2 schema fields changed
    • addedInput schema / properties / registerDomains
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / registrant
      Added value: +{
+  "properties": {
+    "addressLine1": {
+      "maxLength": 500,
+      "minLength": 1,
+      "type": "string"
+    },
+    "city": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "country": {
+      "maxLength": 100,
+      "minLength": 1,
+      "type": "string"
+    },
+    "email": {
+      "format": "email",
+      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+      "type": "string"
+    },
+    "firstName": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "lastName": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "organization": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "phone": {
+      "maxLength": 50,
+      "minLength": 1,
+      "type": "string"
+    },
+    "postalCode": {
+      "maxLength": 20,
+      "minLength": 1,
+      "type": "string"
+    },
+    "state": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "firstName",
+    "lastName",
+    "email",
+    "phone",
+    "addressLine1",
+    "city",
+    "state",
+    "country",
+    "postalCode"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / quoteOnly
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructiveHint=false, so the description carries the behavioral burden and delivers: per-mailbox billing, absence of background retry, deterministic mailbox addresses tied to persona, idempotency semantics, and the exact failure/refusal mode. This is unusually rich disclosure well beyond the annotation.

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?

Front-loaded with the purpose, then flows into inputs, billing, and failure semantics. It is dense and long, but given the 12-param complexity nearly every clause earns its place. Slightly information-dense at the cost of scannability.

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?

No output schema exists, yet the description specifies the return shape { jobId, billing, provisioning?, nextSteps } and the full retry/error workflow. For a high-complexity provisioning tool this is complete enough for an agent to call correctly.

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?

Schema coverage is very low (8%), so the description must compensate, and it does for the ambiguous params: domains/inboxesEach are 'the infra you want to HAVE, not an amount to add', their ordinal fill behavior, distribution as an alternative, and persona determinism on retry. Minor params (senderIdentity, physicalAddress, brand) are left to the schema but are largely self-descriptive.

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?

States a specific verb+resource ('Provision sending infra') and enumerates the concrete sub-actions (buy lookalike domains, create mailboxes, start warmup). This clearly distinguishes it from siblings like configure_byo_domain, remove_mailboxes, and infrastructure_status.

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?

Explicit when/when-not guidance: quoteOnly:true previews cost first, registerDomains:true is required consent before new purchases, and a pending provisioning result needs the caller to retry while capacity_pending routes to contact_operator instead. It even covers the 400 registrar_optin_missing self-correction path.

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

All agent-cold-email 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