Skip to main content
Glama

List conversations

dosai_list_conversations
Read-onlyIdempotent

List dialogs, most recently active first. A dialog is either a chat with one person (kind=direct, chat_id wz_ for WhatsApp, tg_… for Telegram, ig_… for Instagram) or a WhatsApp GROUP the bot is turned on in (kind=group, chat_id wg_, no phone, client_name = the group's subject). Pass kind to get only one of them. Groups are read and written exactly like any other dialog, through get_messages and send_operator_message. Names: client_name is the name the person set in WhatsApp (or the one given in the cabinet); saved_name is how the OWNER saved them in the phone's contacts (WhatsApp only, null = not saved). saved_names_status: ok; book_not_synced (the contacts have not reached us yet, so null means unknown); unavailable (could not ask right now, try again later).

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_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNodirect = a chat with one person, group = a WhatsApp group. Omit for both.
pageNoPage number, default 1.
limitNoRows per page, max 50, default 20.
statusNoopen | resolved | closed.
project_idYesFrom dosai_list_projects.
include_archivedNoInclude archived dialogs, hidden by default.

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. Changed1 schema field changed
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "direct = a chat with one person, group = a WhatsApp group. Omit for both.",
      +  "enum": [
      +    "direct",
      +    "group"
      +  ],
      +  "type": "string"
      +}
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description adds genuinely non-obvious behavior: the default sort order (most recently active first), the chat_id naming patterns per channel, and the distinction between client_name and saved_name plus the three saved_names_status states with their meaning for nulls. That is exactly the kind of context an agent cannot get from the annotations.

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 core behavior and sort order are front-loaded, and the remaining sentences carry real information rather than filler. The second sentence is an overlong run-on with heavy parenthetical nesting, which hurts scanability, but little of the content is genuinely expendable.

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?

With no output schema, the description must carry the return-shape burden, and it does: it names the key fields (client_name, saved_name, saved_names_status) and explains their semantics and null meaning. Combined with schema-documented paging and filtering, an agent has what it needs to call and interpret this tool correctly.

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 the schema already documents kind, page, limit, status, project_id and include_archived, and the description's kind explanation largely restates the schema's own wording. It adds platform-specific chat_id detail, which is more about return values than parameters, and says nothing extra about status, include_archived or paging. Baseline 3 applies.

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 gives a specific verb and resource ('List dialogs, most recently active first') and then defines precisely what a dialog is: a direct chat (with per-platform chat_id prefixes) or a WhatsApp group the bot is enabled in. It is unambiguous about the resource. It does not distinguish itself from plausible siblings such as dosai_list_old_chats or dosai_bulk_conversations, so it falls short of a 5.

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

Usage Guidelines3/5

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

It offers one concrete selection rule ('Pass kind to get only one of them') and useful follow-on routing ('Groups are read and written exactly like any other dialog, through get_messages and send_operator_message'). There is no guidance on when to prefer this over adjacent listing tools, nor on paging through large result sets, so usage is implied rather than fully specified.

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