Skip to main content
Glama

Outil.io

Get outreach readiness

get_outreach_readiness
Read-only

Prospection par e-mail, à lire avant une campagne : boîte (SMTP) ou domaine vérifié utilisé pour l’envoi, lecture des réponses (IMAP : serveur, dernière lecture, erreur), réglages d’envoi, plafond du jour (une nouvelle boîte monte en charge : 10 le premier jour puis +5 par jour), contrôle DNS du domaine d’envoi (SPF, DMARC, MX) avec la correction exacte à faire. Sans boîte : provision_prospecting_mailbox (Outil crée la boîte sur un domaine secondaire, aucune manipulation du client). Tant qu’elle n’est pas active : messages validés puis envoyés depuis le Gmail du client dans son navigateur (MonAssocié). Ne JAMAIS demander au client un réglage SMTP/IMAP, un DNS ou un mot de passe d’application : c’est le travail d’Outil ou de l’agent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_outreach_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds substantial context beyond them: the ramp-up cap (10 first day, +5/day), the DNS checks with the exact fix to apply, and the rule never to ask the client for SMTP/IMAP/DNS/app passwords. This is rich behavioral disclosure for a read tool.

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?

Purpose is front-loaded in the opening clause and every sentence carries information (returns, alternative, fallback, credential rule). Sentences are long and densely packed, which slightly hurts scannability, but nothing 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?

With no output schema, the description must explain what comes back, and it does: mailbox/domain status, IMAP server and last-read/error, sending settings, daily cap, and DNS results with remediation. Combined with the fallback and alternative guidance, an agent has everything needed to call and interpret it.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly spends no space on parameter syntax.

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 (get outreach readiness) and enumerates exactly what is checked: SMTP mailbox or verified domain, IMAP reply reading, sending settings, daily cap, and DNS (SPF/DMARC/MX). An agent can distinguish it from siblings like provision_prospecting_mailbox or set_outreach_settings without opening any 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?

Explicitly says to read it before a campaign, and names the alternative path when no mailbox exists (provision_prospecting_mailbox) plus the fallback behavior while the mailbox is not active. Both when-to-use and the alternative are stated, not inferred.

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.