Skip to main content
Glama
WACrew: WhatsApp AI automation

WACrew: WhatsApp AI automation

silenciar_grupo

Silences or reactivates a WhatsApp chat, group, or DM so messages are still read but it leaves the pending queue and stops alerts. Use for announcement groups or non-response chats.

Instructions

Silencia (true) ou reativa (false) um chat, grupo ou DM: as mensagens continuam sendo coletadas e lidas, mas o chat sai da fila de pendências e não alerta. Use em grupo de aviso ou conversa que não pede resposta. Reversível. Pra tirar da fila só até agora (volta se o cliente escrever), use 'marcar_resolvido'.

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>",
      "silenciar": "<silenciar>"
    },
    "name": "silenciar_grupo"
  }
}

Input Schema

NameRequiredDescriptionDefault
grupoYesslug do grupo (de listar_grupos)
silenciarYestrue = silencia; false = dessilencia

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 the non-obvious consequences (messages still collected and read, chat leaves the pending queue, no alert) and that the action is reversible. It does not cover permissions or whether muting notifies other participants, which are the remaining gaps for a mutation tool.

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?

Dense but front-loaded: the core effect comes first, then the side effects, then the alternative-tool routing. No filler sentences, though the clause about pending-queue semantics is packed tightly enough to require a second read.

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 toggle with no output schema and no annotations, the description covers purpose, side effects, reversibility, and alternative routing, which is essentially everything needed to call it correctly. Only permission/visibility behavior beyond the caller's own view is left unstated.

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 coverage is 100% and both parameters already document 'slug do grupo' and the true/false meaning, so the description's restatement of what true and false do adds little beyond the schema. Baseline 3 applies since the schema does the heavy lifting.

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 pair (silencia/reativa) with the resource (chat, grupo ou DM) and immediately clarifies the scope of the effect. It also names the sibling 'marcar_resolvido' and how it differs, so the agent can distinguish the two without opening any schema.

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 when-to-use guidance ('Use em grupo de aviso ou conversa que não pede resposta') and an explicit when-to-use-the-alternative condition ('Pra tirar da fila só até agora... use marcar_resolvido'). Both the positive case and the routed-away case are covered.

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