WACrew

cancelar_envio

Cancels scheduled or in-progress humanized WhatsApp delivery by group/chat or ticket: unsent messages stop, already-sent messages remain. Use immediately when an operator says cancel or stop.

Instructions

Cancela uma entrega humanizada AGENDADA ou EM ANDAMENTO: o balão que ainda não saiu não sai; o que já saiu fica. Use na hora, SEM confirmar, quando o operador disser 'cancela'/'para'/'não manda'. Por chat (grupo) ou por ticket. Depois chame ler_mensagens no chat pra ver o que chegou a sair antes de reenviar.

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

Input Schema

Name	Required	Description	Default
`grupo`	No	slug, nome exato ou jid do chat cujo envio deve parar
`ticket`	No	id do ticket devolvido pelo responder

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses the destruction boundary (only unsent balloon is cancelled, already-sent messages remain), the no-confirmation policy that authorizes immediate action, and the recovery path via ler_mensagens. That is exactly the behavior an agent needs before invoking a mutation.

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?

Front-loaded with what gets cancelled and what survives, then the trigger and the follow-up. Every clause carries information — trigger synonyms, no-confirmation rule, targeting, next step — with no filler.

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?

For a two-parameter mutation with no annotations and no output schema, nothing an agent needs is missing: what is affected, what is irreversibly already sent, how to target the chat, that no confirmation is required, and how to verify the result afterward.

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 description coverage is 100%, so the baseline is 3; the description adds meaning by framing the two parameters as alternative targeting channels ('por chat (grupo) ou por ticket'), implying a one-of selection rather than requiring both (consistent with 0 required parameters). It does not add syntax or format detail beyond the schema.

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 ('Cancela uma entrega humanizada') and narrows the scope precisely to AGENDADA or EM ANDAMENTO, then explains the boundary condition (the balloon that hasn't left doesn't leave; the one already sent stays). An agent can tell exactly what this tool does and what it cannot undo.

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 trigger conditions (when the operator says 'cancela'/'para'/'não manda'), an explicit behavioral directive (act immediately, do NOT confirm), the two targeting channels (chat/grupo or ticket), and a named follow-up alternative ('chame ler_mensagens ... antes de reenviar'). This is close to a complete operating procedure.

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