Skip to main content
Glama

Turn the bot on or off in a WhatsApp group and set its task

dosai_set_wa_group
Destructive

Configure the bot in one WhatsApp group of the project's number (jid from dosai_list_wa_groups). enabled=true makes the bot read the group and write to it FROM THE OWNER'S NUMBER, members see its messages: confirm with the owner first and only for work groups. mode: mention (answers only when addressed) or watch (reads everything, usually stays silent, does task and reports in one line; requires task). task_from: all, admins or list (then task_from_numbers). daily_check_cap 1-1000 protects the balance. Refused for groups over 100 members and above 5 enabled groups. Requires admin role.

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": {
      "project_id": "<project_id>",
      "jid": "<jid>"
    },
    "name": "dosai_set_wa_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
jidYesGroup id like 120363...@g.us from dosai_list_wa_groups.
modeNo
taskNoWhat the bot does in this group, in plain words (watch mode).
enabledNo
task_fromNo
project_idYesFrom dosai_list_projects.
daily_check_capNo
transcribe_voiceNo
task_from_numbersNoNumbers allowed to give tasks when task_from=list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation it discloses the key behavior: messages are written FROM THE OWNER'S NUMBER and members will see them, which is exactly the consequence an agent must warn about. It also states hard limits — refused above 100 members and above 5 enabled groups — plus the daily_check_cap balance protection and the admin-role prerequisite.

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 critical warning about writing from the owner's number is front-loaded, and every clause carries information (mode semantics, limits, prerequisites). It reads as a dense run-on rather than cleanly structured sentences, but there is no filler to cut.

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 destructive, 9-parameter mutation with no output schema, the definition covers prerequisites (admin role, owner confirmation), effects (visible messages from the owner's number), and rate/quota refusals. Only the meaning of transcribe_voice is left unaddressed, which is a minor omission against the overall coverage.

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?

With only 44% schema coverage across 9 parameters, the description compensates well: it defines enabled, the two mode values, task (required for watch), the three task_from values including the task_from_numbers case, and the 1-1000 daily_check_cap range. The gaps are transcribe_voice, which is undocumented in both schema and description, and project_id, which is only implied.

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?

The description states a specific verb and resource — configure the bot in one WhatsApp group of the project's number — and anchors the jid to dosai_list_wa_groups. It is clear what the tool changes, though it never distinguishes itself from the sibling dosai_toggle_bot_in_conversation, which sounds like an adjacent on/off operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real usage context: confirm with the owner first, only for work groups, admin role required, and it explains when to pick mention vs watch mode, including that watch requires a task. What it lacks is a direct comparison against the sibling toggle tool, so the agent must infer which one applies.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources