Skip to main content
Glama
Sign In
mcp-whatsapp

mcp-whatsapp

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

get_status

Read-onlyIdempotent

Reports WhatsApp connection state, paired account, and read-only mode to diagnose auth or connection errors before retrying other tools. Returns pairing hints when unpaired.

Instructions

Report the WhatsApp connection state and its transition time, paired account, and read-only mode. Read-only with no side effects; use when other tools fail with auth or connection errors. Returns {connected, paired, connection_state, connection_state_since, read_only, own_jid?, own_phone?, hint?}; hint gives the pairing UI when unpaired.

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": "get_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?

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces rather than contradicts them ('Read-only with no side effects'). It adds genuine value beyond the annotations by enumerating the returned fields and explaining that `hint` surfaces the pairing UI when unpaired — meaningful behavioral context for a tool with no output schema.

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?

Three sentences, zero filler: purpose and state first, usage trigger second, return shape and the `hint` field last. The field list is dense but earns its place because no output schema exists. Nothing is repeated from the annotations beyond a brief confirmation.

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?

For a zero-parameter diagnostic tool with no output schema, the description covers what an agent needs: what it reports, when to call it, and exactly what comes back including the optional `hint`. The only omission is the relationship to `pairing_status`, which is a minor gap rather than a blocking one.

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 no parameter semantics to explain and the baseline of 4 applies. The description instead spends its words on return-field semantics, which is the right allocation of space here.

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: reports the WhatsApp connection state plus paired account and read-only mode. The scope is clear enough to distinguish it from messaging/group tools. It does not, however, distinguish itself from the sibling `pairing_status`, which an agent could reasonably confuse with this tool when the connection is unpaired.

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 an explicit trigger: 'use when other tools fail with auth or connection errors,' which is a concrete, actionable condition rather than vague advice. It stops short of naming the near-sibling `pairing_status` as the alternative to reach for when the account is not yet paired, so the routing guidance is incomplete at the edges.

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