Skip to main content
Glama

Outil.io

Set outreach settings

set_outreach_settings

Régler l’envoi de la prospection par e-mail du projet : dailyCap (1-300 par boîte et par jour, 40 par défaut ; rester bas avec une adresse gratuite), hours « 09:00-17:30 », days [1=lundi … 7=dimanche], timeZone (Europe/Paris, Africa/Kinshasa, America/Montreal…), warmup (true par défaut : montée en charge d’une nouvelle boîte), gapSeconds (60-3600 entre deux envois), forwardTo (adresse où transférer les réponses reçues par Outil ; défaut : la boîte qui envoie). Seulement à la demande du client.

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": "set_outreach_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
hoursNo
warmupNo
dailyCapNo
timeZoneNo
forwardToNo
gapSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / forwardTo
      Added value: +{
      +  "format": "email",
      +  "type": "string"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive, non-open-world write, so the safety profile is covered. The description adds genuine behavioral context beyond that: per-parameter defaults (dailyCap 40, warmup true, forwardTo defaults to the sending mailbox) and practical advice ('rester bas avec une adresse gratuite'). It does not disclose whether unset parameters are preserved or reset, which is the one meaningful behavioral gap for a settings mutation.

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 purpose is front-loaded in the first clause, followed by a dense parenthetical per parameter, so scanning is easy and no clause is filler. It is a single long sentence, which makes it heavier to parse than bulleted or multi-sentence structure would be, but the information density justifies the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter settings tool with no output schema and annotations covering only safety, the definition documents every parameter with ranges, defaults and formats, plus a consent guardrail. The remaining gap is whether this is a partial merge or a full replacement of the settings object, which matters given all parameters are optional (0 required).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so thoroughly: it gives meanings, units, valid ranges and defaults for every one of the seven parameters. Critically, it supplies the days mapping '1=lundi … 7=dimanche' and the hours format example '09:00-17:30', neither of which is expressible in the schema, plus timeZone examples and the semantics of gapSeconds and forwardTo.

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?

The description opens with a specific verb and resource: configuring email-outreach sending for the project, then enumerates the seven dials it controls (dailyCap, hours, days, timeZone, warmup, gapSeconds, forwardTo). It is clearly distinguishable from the settings siblings (video, workspace) because it names the outreach-email domain. No explicit differentiation from outreach siblings like get_outreach_readiness or approve_outreach_messages, which keeps it at 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing sentence 'Seulement à la demande du client' gives a real usage guardrail for when this should be invoked. However, no alternative tool is named (e.g., where to check readiness before enabling sending), and there is no when-not guidance beyond the customer-consent rule. Adequate but with clear gaps.

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.