Skip to main content
Glama
Sign In
WhatsApp MCP Server

WhatsApp MCP Server

by HardikCoder45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

connection_status

Check local WhatsApp pairing and connection state. Writes the QR code to the configured local file for linking.

Instructions

Show local pairing and connection state. QR is written to the configured local file.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a real side effect — a QR code is written to a configured local file — which is valuable behavioral information an agent would not otherwise know. However, it says nothing about auth/session requirements, whether the call blocks while waiting for pairing, or whether the operation is read-only in any meaningful sense.

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?

Two short sentences, no filler, and the core purpose is front-loaded ahead of the side-effect detail. Every sentence contributes something.

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

Completeness3/5

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

For a simple zero-parameter status tool this is close to adequate, but with no output schema and no annotations the description should at least sketch what state values can come back or where the 'configured local file' path is set. Those gaps are minor but real.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool is 4. The mention of a 'configured local file' hints at external configuration but does not map to any input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Show local pairing and connection state.' The domain (pairing/connection) is clearly distinct from every sibling, which all deal with chats, messages, or media. It stops short of explicitly naming an alternative or sibling, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as the chat/message tools. The agent must infer that this is the tool to call to check or establish pairing, and whether it should be called before other operations is left unstated.

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