Radar noEixo

Schedule whatsapp message

schedule_whatsapp_message

Agenda uma mensagem de WhatsApp para sair mais tarde numa conversa que JÁ EXISTE com o contato (o mesmo "Agendar envio" do chat). Sai pelo número da conversa, na hora marcada. Texto livre (message) só dentro da janela de 24 h: horário depois do fim da janela é recusado. Para depois da janela, agende um TEMPLATE aprovado: template_name (de list_whatsapp_templates) e template_params com um valor por variável {{1}}, {{2}}…, na ordem; aí message é ignorado. Por padrão cancela sozinha se o cliente responder antes. Até 30 dias para frente e 10 pendentes por conversa.

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": {
      "phone": "<phone>",
      "send_at": "<send_at>"
    },
    "name": "schedule_whatsapp_message"
  }
}

Input Schema

Name	Required	Description
`phone`	Yes	Número do contato com DDD e código do país (ex: 5548988066728). Não precisa do 9º dígito: a normalização é automática.
`message`	No	Texto da mensagem (até 4096 caracteres). Obrigatório sem template_name.
`send_at`	Yes	Quando enviar. "AAAA-MM-DD HH:MM" é lido como horário de Brasília (ex: "2026-10-25 09:00"); também aceita ISO 8601 com fuso.
`template_name`	No	Opcional: nome do template aprovado, para horário depois da janela de 24 h.
`target_user_id`	No	ID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.
`cancel_if_reply`	No	Cancelar se o cliente responder antes (padrão true).
`template_params`	No	Valores das variáveis do corpo do template, na ordem ({{1}}, {{2}}…).
`template_language`	No	Idioma do template (padrão: o do template aprovado, normalmente pt_BR).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses the 24h-window rejection rule, that message is ignored when template_name is supplied, the default cancel_if_reply=true behavior, the 30-day/10-pending caps, and the admin-only nature of target_user_id. Annotations only cover the read/write and open-world profile, so this added context is the valuable part.

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 core fact (schedule for later in an existing conversation) is front-loaded, and every sentence carries operational information. It is a dense run-on paragraph, though, and the window/template rules could be split for faster scanning.

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 mutation tool with rich annotations, the description covers preconditions, limits, and failure modes thoroughly. It does not say what a successful call returns (e.g., the scheduled message id), and there is no output schema to cover that gap.

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 field-level meaning is already documented. The description still adds cross-parameter logic not present in the schema: message is required without template_name and ignored with it, and template_params must map one value per {{1}}, {{2}}… in order.

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 ('Agenda uma mensagem de WhatsApp') plus the key scoping constraint that the conversation must already exist and the send happens later, which separates it from an immediate-send tool. It does not name the immediate sibling (send_whatsapp_message) explicitly, leaving that differentiation partly inferential.

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 gives when-to-use for free text (inside the 24h window), when it will be refused (scheduling past the window end), and the required alternative (an approved template via template_name from list_whatsapp_templates with ordered template_params). It also states the default auto-cancel behavior and the operating limits (30 days ahead, 10 pending per conversation).

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

All Radar noEixo 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?