Skip to main content
Glama
Sign In
askmywa

askmywa

by Ruwad-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

WhatsApp status

whatsapp_status
Read-onlyIdempotent

Check whether WhatsApp is set up on this computer—background service, phone link, connection, archive size, and send folder—and get plain next-step guidance when setup is missing.

Instructions

Report whether WhatsApp is set up on this computer: background service, link with the phone, connection, archive size, and the folder files can be sent from. next_step says in plain words what to do when something is missing. Call it first when another WhatsApp tool fails.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
chatsYes
linkedYesthis computer is linked to a WhatsApp account
accountNothe linked account
messagesYes
connectedYescurrently connected to WhatsApp
next_stepYeswhat to do next, in plain words
send_folderNofiles must be in this folder to be sent
service_runningYesthe background service answers
service_installedYesthe background service is registered to start at login
pairing_in_progressNoa pairing code is waiting to be typed on the phone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the specific signals inspected and the presence of a 'next_step' field that translates failures into plain-language remediation, which is the key output an agent should read.

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 short sentences, front-loaded with the purpose, then the return contents, then the usage trigger. Every clause carries information and nothing is repeated from the title or annotations.

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?

An output schema exists so return values need not be explained, yet the description still names the checked signals and highlights next_step as the field to act on, which is the highest-value guidance for this diagnostic tool. Nothing needed to call it correctly is missing.

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, and the 100% schema coverage baseline applies. The description correctly spends no words on arguments and instead describes the report contents.

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?

The description opens with a specific verb and resource ('Report whether WhatsApp is set up on this computer') and then enumerates exactly what is reported: background service, phone link, connection, archive size, and the send-from folder. That enumeration makes it instantly distinguishable from action-oriented siblings like connect_whatsapp or send_message.

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?

It gives an explicit trigger — 'Call it first when another WhatsApp tool fails' — which is exactly the guidance an agent needs for a diagnostic tool. It does not state when not to call it (e.g. whether a healthy-state check before a first send is wasteful), but the core routing rule is present and unambiguous.

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