WACrew: WhatsApp AI automation

marcar_resolvido

Marks a WhatsApp chat as resolved until a set time, removing it from the pending queue; any client message after that returns it to the queue. Sends no reply or notification.

Instructions

Tira um chat (grupo ou DM) da fila de pendências marcando-o como resolvido até um momento: mensagem de cliente que chegar DEPOIS faz ele voltar pra fila. Não envia nada nem avisa o cliente. Sem 'ate', usa agora. Pra parar de alertar o chat de vez, use 'silenciar_grupo'.

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": {
      "grupo": "<grupo>"
    },
    "name": "marcar_resolvido"
  }
}

Input Schema

Name	Required	Description	Default
`ate`	No	ISO timestamp 'resolvido até aqui'; default = agora
`grupo`	Yes	slug do grupo (de listar_grupos)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses side effects (sends nothing, does not notify the client), the reactivation rule (a client message arriving after the moment puts it back in the queue), and the default for the 'ate' parameter. It stops short of covering permission requirements or error behavior.

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?

Three short sentences, front-loaded with the core action and reactivation rule, then the side-effect clarification, then the alternative-tool escape hatch. Every sentence earns its place.

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 two-parameter mutation tool with no annotations and no output schema, the description covers what the agent needs to call it correctly, including side effects and reactivation semantics. It could say a bit more about the return value or failure modes, but nothing critical is missing.

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 both parameters are already documented. The description adds the default behavior ('sem ate, usa agora'), which mildly restates the schema default, but adds no syntax or format detail beyond it. Baseline 3 is appropriate.

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 and resource: removes a chat (group or DM) from the pending queue by marking it resolved. It distinguishes itself from the sibling silenciar_grupo by naming it explicitly, so an agent can tell the two apart without reading schemas.

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 the condition to use it (take a chat out of the pending queue until a moment) and an explicit alternative: to stop alerting the chat permanently, use 'silenciar_grupo'. Nothing is left to inference.

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