Skip to main content
Glama
Sign In

WABRA — WhatsApp Business for Brazil

by io.github.Amigov2
OverviewDiscussionsAdmin

Enviar WhatsApp

send_whatsapp_message

Envia uma mensagem WhatsApp Business via WABRA. Requer que o destinatário tenha opt-in ou esteja dentro da janela de 24h.

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": {
      "to": "<to>",
      "text": "<text>"
    },
    "name": "send_whatsapp_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesNúmero do destinatário no formato E.164 (ex: +5521999999999)
textYesTexto da mensagem (máximo 4096 caracteres)
templateNoNome do template Meta aprovado (obrigatório fora da janela 24h)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the external send channel and the WhatsApp compliance constraint (opt-in / 24h window), but says nothing about delivery semantics, failure modes (e.g. what happens when opt-in is absent), rate limits, or the response shape.

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?

Two short sentences, zero padding, with the core action stated first and the constraint immediately after. Nothing repeated and nothing wasted.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers the key compliance prerequisite but omits what the agent gets back and how failures are signalled. Adequate but with clear gaps given the complexity of an external messaging send.

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

Parameters3/5

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

Schema description coverage is 100%, so E.164 formatting, the 4096-char limit, and the template-name requirement are already documented in the schema. The description adds no parameter-level meaning beyond structured data, so baseline 3 applies.

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 ('Envia uma mensagem WhatsApp Business') plus the provider (WABRA). It is clearly distinct from the read-oriented siblings (get_messages, list_conversations, search_contacts), though it never names them explicitly.

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?

Gives a real precondition (recipient must have opt-in or be inside the 24h window), which is useful context for deciding whether to call it. However, it offers no explicit guidance on choosing between the plain text path and the template path, nor does it address sibling alternatives.

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

All WABRA — WhatsApp Business for Brazil toolsInspect
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