Skip to main content
Glama
WhatsApp MCP Server

WhatsApp MCP Server

check_connection_status

Verifies WhatsApp installation, database access, and macOS Full Disk Access, then returns chat, message, media counts and latest message date with setup guidance if permissions are missing.

Instructions

Check whether WhatsApp.app is installed, if the ChatStorage.sqlite database is accessible, and whether macOS Full Disk Access is granted (with setup instructions if needed). Returns summary statistics including chat count, message count, media count, and latest message date.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the tool performs non-mutating environment checks, enumerates the returned statistics (chat count, message count, media count, latest message date), and notes that remediation guidance is included when Full Disk Access is missing. It does not say what the result looks like when a check fails versus succeeds (error vs. flag), which keeps it below a 5.

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 sentences, front-loaded with the conditions checked and followed by the return summary. Every clause carries distinct information with no 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 zero-parameter diagnostic with no annotations and no output schema, the description covers both the checks performed and the shape of the response, which is most of what an agent needs. The one residual gap is the failure/partial-success reporting format, which an agent would want before branching on the result.

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 per the baseline no parameter explanation is required. The description correctly adds no irrelevant argument detail and instead spends its words on behavior.

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?

Names a specific verb ("Check") and three concrete conditions: WhatsApp.app installation, ChatStorage.sqlite accessibility, and macOS Full Disk Access. It also states the return payload, which clearly distinguishes this diagnostic tool from the sibling data tools (list_chats, list_messages, search_messages).

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

Usage Guidelines3/5

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

The mention of "setup instructions if needed" implies this is a pre-flight/environment-verification tool, but it never explicitly says to call it before other tools or when to prefer it over alternatives. Usage is inferable rather than stated.

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