Skip to main content
Glama
Sign In
ChatPush MCP Server

ChatPush MCP Server

Official
by ChatPush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get messenger authorization link

get_messenger_auth_link

Get a QR-code link to connect a WhatsApp or personal Telegram account to ChatPush when sending fails due to an unconnected messenger or during initial setup.

Instructions

Get a link to the QR-code page that connects a WhatsApp or personal Telegram account to ChatPush. Open the link in a browser and scan the code with the phone that will send messages.

Use it when sending fails because the messenger is not connected (WhatsApp session not started, Telegram not authorized), or when setting the account up for the first time. Check the result afterwards with get_account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "messenger": "<messenger>"
    },
    "name": "get_messenger_auth_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
messengerYesMessenger to connect: "whatsapp" for WhatsApp, "tdlib" for a personal Telegram account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, destructiveHint=false, so the agent knows external state is involved. The description adds the crucial operational detail that a human must open the URL in a browser and scan with the target phone, which no annotation conveys. It does not explain whether calling it starts a server-side session or how long the link remains valid, which is the remaining gap given readOnlyHint=false.

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 what the tool returns and what to do with it, then the usage conditions. Two tight paragraphs with little waste; the parenthetical error states are informative rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, the description covers purpose, trigger conditions, and the required human step. It could go further by stating that the return value is a URL and whether the link is single-use or expires, which matters for an authorization flow.

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 enum values are already documented in the schema (whatsapp, tdlib). The description only restates the mapping ('WhatsApp or personal Telegram account') without adding format or behavioral nuance. Baseline 3 applies since the schema does the work.

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 concrete verb and resource: fetches a link to a QR-code page that connects a WhatsApp or personal Telegram account. The scope (which messenger, what the link is for) is stated precisely enough that it is distinguishable from the sibling get_account, which it references as a separate step.

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 explicit triggers: sending fails because the messenger is not connected (WhatsApp session not started, Telegram not authorized) or first-time setup. It also names the follow-up action (verify with get_account). No explicit 'do not use when already connected' exclusion, but the conditions are clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools