Skip to main content
Glama

List the WhatsApp groups of the project's number

dosai_list_wa_groups
Read-onlyIdempotent

List WhatsApp groups the project's number is in, with the bot settings of each: enabled (the bot sees the group), mode (mention = answers when its number is tagged or its message is replied to; watch = reads the group and does the group task), task, who gives tasks, daily check cap. By default the bot sees no group. live=true asks WhatsApp for the current list (needs the number connected); without it only groups that already have settings are returned. An enabled group also carries conversation_id: that is the dialog that holds its messages, for get_messages and send_operator_message. Limits: at most 5 enabled groups per project, groups of up to 100 members.

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

Input Schema

NameRequiredDescriptionDefault
liveNotrue = fetch the number's current group list from WhatsApp (default true).
project_idYesFrom dosai_list_projects.

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.6/5.0
Behavior5/5

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

Annotations only declare a safe read, but the description adds substantial behavior: the default state is that the bot sees no group, live listing depends on connection status, and there are hard limits (5 enabled groups, 100 members). It also explains that enabled groups carry a conversation_id usable by get_messages and send_operator_message, which is real cross-tool operational context.

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?

Front-loaded with the purpose, then defaults, then limits — a sensible order. It is one dense paragraph with several parenthetical definitions, but each sentence carries operational information rather than 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?

There is no output schema, and the description compensates by enumerating the fields returned per group (enabled, mode, task, task assigner, daily cap, conversation_id). Combined with the defaults and quota limits, an agent has enough to call it correctly and interpret the result.

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 coverage is 100%, so baseline is 3, and the description goes beyond it by explaining the practical consequence of live: what is fetched from WhatsApp, what the prerequisite is, and what a fallback call returns. It also decodes the 'mode' values (mention vs watch) and other returned fields, though the project_id parameter itself gets no additional explanation.

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 ('List WhatsApp groups the project's number is in') and immediately qualifies the payload ('with the bot settings of each'). This clearly separates it from mutating siblings like dosai_set_wa_group and from dosai_get_wa_group_participants.

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?

Gives clear context for the two operating modes: live=true queries WhatsApp and requires the number to be connected, while omitting it returns only groups that already carry settings. It does not name an alternative tool for enabling or configuring groups, so guidance is contextual rather than fully comparative.

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