Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Bring a number back online

connect_number
Idempotent

Reconnect a WhatsApp number that is currently offline.

Uses the credentials already stored for the number, so no QR code and no human are involved. Use it when get_number reports disconnected and you want to send.

Returns immediately, before the connection is established. The answer has the number's alias, status set to connecting and at, the moment the request was accepted. The number reaches connected a few seconds later: poll get_number, which stays the source of the current status and of its own at, rather than assuming it worked.

It works the same on every number and never charges. On an extra number scheduled for removal it does not change the removal: the number keeps working until its date. Cancelling a removal is not available to agents.

This cannot rescue a revoked number: WhatsApp ended that link and a person with the phone has to pair it again.

Calling it again changes nothing further. A number that is already connected or connecting answers with an already_connected or already_connecting error, which means the goal is met, not that the call failed.

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": "connect_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.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the asynchronous return semantics (status `connecting`, then `connected` seconds later), the error-as-success pattern for `already_connected`/`already_connecting`, that it never charges, and how it interacts with a scheduled removal. The idempotency claim is consistent with idempotentHint=true, and the 'cannot rescue a revoked number' limit is exactly the kind of failure mode an agent needs.

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

Conciseness5/5

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

Long for a one-parameter tool, but front-loaded with the core action and then organized into distinct, non-overlapping blocks: precondition, return semantics, side effects, limitations, idempotency. No sentence is filler; each answers a question an agent would otherwise have to guess at.

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?

Even though an output schema exists, the description supplies the crucial async contract that a schema cannot convey — that the immediate response is not the final state and polling is required. Combined with the mutation/removal caveats and revoked-number limit, nothing needed to call this 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% and the single `number_alias` parameter is fully documented there, including the `num_…` id form and the pointer to `list_numbers`. The description only adds the general note that behavior is the same on every number, which is mild value over the schema — baseline 3 applies.

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 ('Reconnect a WhatsApp number that is currently offline') with the precondition baked in. It is clearly the inverse of the sibling disconnect_number, and the title alone plus the first sentence makes the scope unambiguous.

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?

Explicitly names the trigger ('Use it when `get_number` reports `disconnected` and you want to send') and the follow-up action ('poll `get_number`'). It also names the case where the tool cannot help (`revoked` numbers require a human with the phone), so the agent knows both when to use it and when not to.

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.