Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get one number and its connection status

get_number
Read-onlyIdempotent

Check one WhatsApp number: its phone number, status, and when that status began.

id (num_…) is the number's permanent identifier. The alias can be renamed, the id cannot. Either one works as number_alias.

connected means it can send right now. connecting means a connection was just requested and is being set up; check again in a few seconds. reconnecting means the number lost its connection and Turbo Notify is bringing it back by itself: there is nothing to do but wait and check again. Until it is connected again, sends are refused with number_not_connected. disconnected means the link to the phone still exists but the number is offline, so connect_number brings it back. inactive is the same for a number that was linked and has not been brought online yet: connect_number brings it online too. pending means the number was never linked to a phone, and no_main_number (what a brand-new account gets for main, and list_numbers is empty) means there is no number at all yet: either way a person has to link it from the Numbers page of the dashboard, so tell them and do not retry the send meanwhile. revoked means WhatsApp ended the link (the device was removed under Linked devices on the phone, or the phone went more than 14 days without being used) or another connection took it over. failed means a pairing did not complete; on an extra number reason says why (for example pairing_timeout when the code or QR code was not used in time, paired_phone_mismatch when another WhatsApp used it). Either one has to be paired again by a person holding that phone: from the dashboard (main or extra number) or, for an extra number, through the API's pairing endpoint, by code or by QR code. No tool here pairs a number: it needs a person with the phone.

pairing means a person is pairing the number right now. The code or QR code they use is not part of this answer: it belongs to that person. Check again later; the status moves to connected, or to failed (with a reason on an extra number).

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

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is added context, and it does add real behavior: sends refused with number_not_connected while reconnecting, statuses resolving on their own, and the fact that pairing requires a human with the phone. The bulk of the text, however, is a per-status lookup table that largely duplicates what the tool returns, so it informs interpretation more than it discloses novel runtime behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the backticked status tokens make it scannable, but the definition runs to roughly 350 words for a one-parameter read. Several status paragraphs (pairing, pending, revoked/failed) are long and could be condensed since the output schema already carries the status set.

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 status-read tool with an output schema, annotations and a fully documented parameter, nothing material is missing — the description even explains recovery paths and human-in-the-loop requirements that would otherwise be silent.

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 coverage is 100% and the single `number_alias` parameter is already documented there, including the `main` default and the `num_…` id form. The description reinforces the id-vs-alias distinction (aliases rename, ids do not), which is a small amount of meaning beyond the schema; 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?

First sentence gives a specific verb and resource with scope: 'Check one WhatsApp number: its phone number, status, and when that status began.' It is clearly a single-resource read, distinguishable from list_numbers, which it explicitly names as the way to enumerate aliases.

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 routes the agent in nearly every state: connect_number for disconnected/inactive, a person via the dashboard for pending/no_main_number, the pairing endpoint or dashboard for failed/revoked, and explicit 'do not retry the send meanwhile' / 'no tool here pairs a number' exclusions. The when-not guidance is unusually explicit.

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.