WarmInboxes Free MCP: Fleet Planner

Price a number of inboxes (quote)

quote_inboxes

Read-onlyIdempotent

Prices a given number of inboxes at WarmInboxes' published prices: the domains (or Azure tenants) they sit on, daily sending capacity at the provider's pace, monthly cost and delivery time. Use it when the person already knows the count ("preview 100 inboxes"); for a send volume use plan_infrastructure. Azure is sold by the tenant, so a count that does not fill one is quoted for the tenants it needs, with a note. A quote only: it orders nothing, and the exact preview with real domain and mailbox names is in the app or on WarmInboxes Infrastructure MCP.

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": {
      "inboxes": "<inboxes>"
    },
    "name": "quote_inboxes"
  }
}

Input Schema

Name	Required	Description
`billing`	No	Prewarmed commitment length. Longer is cheaper. Defaults to monthly.
`inboxes`	Yes	How many inboxes, 1 to 20,000.
`provider`	No	Google Workspace, Microsoft 365, or Azure (Microsoft tenants). Defaults to google.
`prewarmed`	No	true for prewarmed inboxes, false for fresh (14-21 day warmup, cheaper). Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: it orders nothing, Azure counts are rounded up to tenant needs with a note, and exact domain/mailbox previews happen elsewhere.

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 front-loaded with the core pricing action and then adds only high-value context: alternative tool, Azure edge case, and quote-only limitation. Every sentence earns its place and the example ("preview 100 inboxes") clarifies intent efficiently.

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?

There is no output schema, but the description explains the return dimensions (domains/tenants, daily sending capacity, monthly cost, delivery time). It also covers limitations and alternatives, giving an agent enough context to call and interpret the tool 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 description coverage is 100%, so the schema already documents all four parameters; the baseline is 3. The description adds useful semantics for provider/inboxes by explaining Azure tenant-based quoting when the count does not fill a tenant, though it does not add detail about billing or prewarmed beyond the schema.

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 and resource: "Prices a given number of inboxes" and lists the quote outputs (domains/tenants, sending capacity, monthly cost, delivery time). It also distinguishes itself from plan_infrastructure by count versus send volume, so an agent can select it without opening the schema.

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 when-to-use guidance ("when the person already knows the count") and names the alternative for a different input mode ("for a send volume use plan_infrastructure"). It also clarifies that the tool only quotes and does not order, which is an important usage boundary.

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

All WarmInboxes Free MCP: Fleet Planner 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.

Resources

Need Help?