Skip to main content
Glama

WarmInboxes Free MCP

Inboxes and domains for a send volume (estimate)

plan_infrastructure
Read-onlyIdempotent

Estimates how many inboxes and domains a daily cold email volume needs and the monthly cost at WarmInboxes' published prices. Inputs: emailsPerDay; optionally the provider (esp), prewarmed or fresh, billing cycle, emails per inbox per day and inboxes per domain. With currentInboxes (healthy inboxes already sending) it sizes only the shortfall between their capacity and the target, and says when nothing needs adding; with reservePercent it adds that much spare capacity on top, and only when asked: no reserve is recommended by default. With dealValue (and optionally closeRate and positiveRate) it adds a revenue and ROI projection from those inputs. Assumes the provider's default daily pace per inbox unless emailsPerMailbox is given, and 22 sending days a month. The result is a planning estimate: it orders nothing, does not guarantee placement or replies, and its revenue figures follow only from the rates supplied.

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": {
      "emailsPerDay": "<emailsPerDay>"
    },
    "name": "plan_infrastructure"
  }
}

Input Schema

NameRequiredDescriptionDefault
espNoSending platform. Defaults to google.
billingNoPrewarmed commitment length. Longer cycles are cheaper. Defaults to monthly. Google and Microsoft are billed per inbox; Azure is billed per tenant, flat, whatever is on the tenant.
rotationNoRest half the fleet at any moment, which doubles the inboxes bought. Defaults to false.
closeRateNoPercent of positive replies that close. Defaults to 10.
dealValueNoAverage deal size. Supply it to get replies, deals, revenue and ROI.
prewarmedNotrue for prewarmed inboxes (ready to send on delivery), false for fresh (14-21 day warmup, about a third the price). Defaults to true.
emailsPerDayYesTarget cold emails per day, e.g. 500.
positiveRateNoPercent of sends that reply positively. Defaults to 1.
currentInboxesNoHealthy inboxes already sending on this platform. When given, only the shortfall between their capacity and emailsPerDay is sized.
reservePercentNoSpare capacity to add on top of the target, 0 to 100, only when the person asks for a reserve. Defaults to 0.
emailsPerMailboxNoDaily sends per inbox. Defaults to the platform's safe pace: 15 Google, 8 Microsoft, 2 Azure.
inboxesPerTenantNoFresh Azure only: how densely a tenant is packed. Also sets the pace, since a lighter tenant sends more per inbox (25/6, 50/4, 100/2). Defaults to 100.
mailboxesPerDomainNoFresh Google and Microsoft only. Defaults to 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / inboxesPerTenant / enum
      Previous value: -[
      -  25,
      -  50,
      -  100
      -]New value: +[
      +  15,
      +  25,
      +  50
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / currentInboxes
      Added value: +{
      +  "description": "Healthy inboxes already sending on this platform. When given, only the shortfall between their capacity and emailsPerDay is sized.",
      +  "type": "number"
      +}
    • addedInput schema / properties / reservePercent
      Added value: +{
      +  "description": "Spare capacity to add on top of the target, 0 to 100, only when the person asks for a reserve. Defaults to 0.",
      +  "type": "number"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / prewarmed / description
      Previous value: -"true for prewarmed inboxes (send today), false for fresh (14-21 day warmup, about a third the price). Defaults to true."New value: +"true for prewarmed inboxes (ready to send on delivery), false for fresh (14-21 day warmup, about a third the price). Defaults to true."
  4. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: it orders nothing, guarantees no placement or replies, assumes 22 sending days a month and the platform's default pace, and derives revenue only from supplied rates. That is solid added value, though it does not describe the shape of the returned estimate.

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?

Dense but front-loaded: the purpose and cost estimate come first, then the optional-input behaviors, then the assumptions and disclaimers. It is a long single paragraph, but nearly every clause carries decision-relevant information, so little is wasted.

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?

For a 13-parameter planning tool with no output schema, the description covers the key behaviors (shortfall sizing, opt-in reserve, revenue projection), the assumptions behind the numbers, and the limits of the result. An agent has enough to decide when to call it and how to interpret the estimate.

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 100%, so the baseline is 3, but the description adds real meaning on top: currentInboxes sizes only the shortfall and reports when nothing needs adding, reservePercent is opt-in spare capacity, and dealValue triggers the revenue/ROI block. It also flags the default-pace and 22-day assumptions that govern emailsPerMailbox and cost.

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?

States a specific verb and resource: estimates inboxes, domains and monthly cost for a given daily cold email volume. The scope is unambiguous, but it never names a sibling (e.g. quote_inboxes or plan_rotation) to differentiate itself, so it stops short of a 5.

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?

Gives explicit conditional guidance: use currentInboxes to size only the shortfall, use reservePercent only when a reserve is asked for, and add dealValue (with closeRate/positiveRate) to get the revenue projection. It also states the default behavior (no reserve recommended) so the agent knows what happens when those inputs are omitted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources