Skip to main content
Glama

Account: Connection status

account_connection_status
Destructive

Check an in-conversation WhatsApp/Telegram connection started with whatsapp_connect or telegram_connect. Returns pending (with the current QR code image or pairing code, refreshed when it changed), connected, expired or failed. Poll every 10-20 seconds until the status is connected, then retry the user's original request. Omit intent_id to check the most recent attempt. This also expires stale connection intents and may create a Hosted Auth recovery link for a finished attempt.

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

Input Schema

NameRequiredDescriptionDefault
intent_idNointent_id returned by whatsapp_connect/telegram_connect. Omit for the latest attempt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations mark this destructiveHint=true and idempotentHint=false, which is counterintuitive for a 'status check'; the description earns its keep by explaining why — it expires stale connection intents and may mint a Hosted Auth recovery link. It also enumerates the return states (pending with QR/pairing code refreshed on change, connected, expired, failed), which no output schema provides.

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-loaded with the purpose, then statuses, then polling cadence, then the default-parameter rule, then side effects — a sensible order. The final sentence bundles two distinct side effects (expiring stale intents, creating a recovery link) in one clause, which is slightly dense but not wasteful.

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 carries the full return-value burden and does so by listing all four statuses and the QR/pairing-code payload. Polling cadence and side effects complete everything an agent needs to drive the connection flow to completion.

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 intent_id parameter is already documented in the schema, including the omit behavior. The description restates that fallback but adds no new syntax, format, or validation detail, so 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 ('Check an in-conversation WhatsApp/Telegram connection') and ties it back to the exact siblings that create the connection (whatsapp_connect, telegram_connect). An agent can select this without opening any other definition.

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?

Gives concrete operating instructions: poll every 10-20 seconds, stop when connected, then retry the user's original request. Also specifies the omit-intent_id fallback for checking the latest attempt, so both the timing and the default case are covered.

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.