Skip to main content
Glama

Outil.io

Provision prospecting mailbox

provision_prospecting_mailbox

Créer la boîte e-mail de prospection du client SANS aucune manipulation de sa part : Outil ajoute le domaine à sa messagerie (Zoho Mail), écrit tous les DNS (vérification, MX, SPF, DKIM, DMARC), crée la boîte {localPart}@{domain} et l’enregistre comme connexion SMTP de l’espace ; la prospection part ensuite d’elle avec montée en charge automatique. domain = domaine SECONDAIRE réservé à la prospection (ex. dupont-plomberie.fr pour dupontplomberie.fr), géré par Outil (acheté par Outil) ; un domaine qui reçoit déjà des e-mails ailleurs est refusé. Une boîte par espace. Asynchrone : suivre avec get_mailbox_provisioning (minutes à quelques heures, propagation DNS). Si la réponse dit started:false avec needed, ce sont des accès à fournir par l’équipe Outil, pas par le client.

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": {
      "domain": "<domain>"
    },
    "name": "provision_prospecting_mailbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
localPartNo
displayNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the description adds real context beyond them: the operation is asynchronous, DNS propagation takes minutes to hours, started:false with needed means Outil-side credentials rather than client action. It does not say what happens if provisioning fails partway (e.g. partially written DNS records) or how to recover, which keeps it short of a 5.

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 main action is front-loaded and the paragraph is dense with operational detail rather than filler; the async warning and the 'started:false / needed' caveat are placed at the end where they are needed. A few clauses are redundant (repeating that the domain is managed/bought by Outil), keeping it from a 5.

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?

With no output schema, the description still tells the agent what happens next (poll get_mailbox_provisioning, expect minutes to hours) and how to interpret the started:false/needed response. Nothing essential for calling and handling this tool is missing.

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 0%, so the description must compensate: it defines domain precisely (secondary prospecting domain, with an example) and implicitly defines localPart by specifying the mailbox as {localPart}@{domain}. displayName is left unexplained, but it is an optional, self-descriptive field.

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 (create the prospecting mailbox) and enumerates the concrete actions taken: adding the domain to Zoho Mail, writing verification/MX/SPF/DKIM/DMARC records, creating {localPart}@{domain} and registering it as the workspace SMTP connection. This is clearly distinguishable from the sibling get_mailbox_provisioning, which is named as the follow-up tool.

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 preconditions and exclusions: the domain must be a secondary domain managed/bought by Outil and reserved for prospecting, a domain already receiving mail elsewhere is refused, and one mailbox per workspace. It also routes the agent to get_mailbox_provisioning for asynchronous follow-up.

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.