Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Show the typing indicator in a conversation

send_typing_indicator

Show "typing…" to a recipient on WhatsApp while you prepare an answer.

Set exactly one recipient: number, group_id, or contact_id.

Useful before a reply that takes a few seconds to compose, so the person on the other end sees something is happening. It expires on its own, so clearing it is optional: pass is_typing=false only if you decide not to answer after all and want the indicator gone at once.

There is no duration argument. WhatsApp decides how long it lives.

Starting to type also opens the conversation: the number appears online, its unread messages in that conversation are marked as read, and after a short pause "typing…" appears, so it never shows over unread messages. Stopping (is_typing=false) only clears the indicator and reads nothing. Opening the conversation this way is automatic and uses no quota of its own.

Needs a plan that includes the typing indicator, and showing it in a group needs one that includes group messaging as well. Without either, this answers payment_required: feature_not_available, and the answer will not change by retrying.

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": "send_typing_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNoRecipient phone number in E.164 form, digits only, country code first (e.g. `5511999999999`). Set exactly one of `number`, `group_id` or `contact_id`.
group_idNoRecipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that.
is_typingNo`true` shows "typing…" (the default), `false` clears it.
contact_idNoRecipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / contact_id / description
      Previous value: -"Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one inbox does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`."New value: +"Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`."
    • changedInput schema / properties / group_id / description
      Previous value: -"Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one inbox does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that."New value: +"Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing non-obvious side effects: the recipient's number appears online, unread messages in that conversation are marked as read, and the indicator only appears after a short pause so it never shows over unread messages. It also rules out a duration argument, explains auto-expiry, and documents the exact failure mode (`payment_required: feature_not_available`) with a note that retrying is futile.

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-loads the purpose and the recipient constraint before the optional background, and each paragraph covers one concern. Some content, notably the group-messaging plan requirement and the exactly-one-recipient rule, is repeated from the schema, costing a little length without adding meaning.

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 five-parameter tool with an output schema and full schema coverage, the description supplies everything an agent still needs: side effects, expiry semantics, plan gating, and the specific error string. Nothing required to invoke it correctly is missing.

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 all five parameters are already documented in structured form. The description reinforces the mutual-exclusivity rule for number/group_id/contact_id and explains the is_typing default behavior, but adds little syntax or format detail the schema does not already carry. Baseline 3 is appropriate.

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 — show the "typing…" indicator to a WhatsApp recipient — and frames it as a preparatory signal before a reply. The scope is unmistakable and clearly distinct from the sibling send_* tools, which deliver actual content.

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 a concrete when-to-use condition ("before a reply that takes a few seconds to compose") and a when-to-use-the-inverse condition ("pass is_typing=false only if you decide not to answer after all"). It also states plan prerequisites. It does not name a sibling alternative for cases where the agent should just send the message, but the guidance is clear enough to act on.

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.