Skip to main content
Glama

Choose chats to capture

choose_chats_to_capture
Read-onlyIdempotent

Show the user a picker of a connected number's WhatsApp chats, where they search, tick the ones they want and start capturing their new messages from today. Use it when the user wants to choose which chats to capture, or to capture many at once, instead of listing and starting them yourself; it starts nothing on its own. Narrow it to what the user asked with query, kind and active_since, as in list_capturable_chats; phone may be omitted when the user has a single number. Follow the first text of its result: where the picker shows, end your turn, and the user's choice arrives as the next message. If this tool answers an error whose code is currency_selection_required, the user has not confirmed the account's currency: show them the action_url and do not retry until they say it is done.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "choose_chats_to_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional: "direct" for one-to-one chats only, "group" for groups only.
phoneNoThe connected number, as returned by list_connected_numbers. Omit it when the user has a single connected number.
queryNoOptional substring of the chat names to show (case- and accent-insensitive).
active_sinceNoOptional YYYY-MM-DD on the phone's calendar: only chats with a message on or after it.

Output Schema

NameRequiredDescriptionDefault
kindNo
chatsNo
phoneNoThe number the picker captures for.
queryNo
totalNoHow many chats match the filters.
localeNoThe Werify account's language as a BCP 47 tag, for the widget's own text.
next_cursorNoThe next page, for list_capturable_chats; null on the last page.
active_sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description reinforces this with 'it starts nothing on its own'. It adds valuable interaction semantics (turn-ending, deferred user reply) and an error path for currency_selection_required with action_url and no-retry guidance. However, it doesn't say what the result's first text looks like or what happens to chats already captured, leaving part of the return behavior implicit despite an output schema existing.

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?

It is front-loaded with the action, then usage, then parameters, then the follow-up and error protocol, so the structure is sound and nearly every sentence carries operational weight. It is dense and multi-clause, with the currency error sentence adding length that only some calls will need.

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 zero-required-parameter picker with an output schema, the description covers invocation context, parameter narrowing, the human-in-the-loop turn boundary, and a specific recoverable error code. An agent has everything needed to call it and to handle the response correctly.

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 the baseline is 3, but the description adds routing meaning: query/kind/active_since narrow the picker 'as in list_capturable_chats', and phone may be omitted for single-number users. That connects each parameter to user intent rather than just restating the schema.

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?

The description opens with a concrete verb and resource: show the user a picker of a connected number's WhatsApp chats where they search, tick, and start capturing new messages from today. It explicitly separates itself from the sibling pair list_capturable_chats/start_capture by noting it 'starts nothing on its own' and replaces 'listing and starting them yourself'.

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?

It states exactly when to use it (user wants to choose chats, or capture many at once) and when not to (instead of listing and starting them yourself). It also gives the operational protocol: end your turn when the picker shows, and the user's choice arrives as the next message.

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