Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Get the WhatsApp connection status

get_status
Read-onlyIdempotent

Check WhatsApp account connection, sync freshness, webhook delivery, and versions to diagnose not-connected, not-linked, or sync-in-progress issues.

Instructions

Whether the account works: status (connected, not_linked, linking with its pairing code…), sync, how fresh the history is, webhook delivery, versions. accounts lists every account, with default. Call it on NOT_CONNECTED, NOT_LINKED or SYNC_IN_PROGRESS.

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
account_idNo
include_pictureNoAdd picture_url, the account's own profile photo (the link expires)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / include_picture
      Added value: +{
      +  "default": false,
      +  "description": "Add picture_url, the account's own profile photo (the link expires)",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"
  5. Changed2 schema fields changedv0.15.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  6. First observedv0.9.3

TDQS

A3.6/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 closed-world, so the safety profile is covered. The description adds value beyond that by describing the returned facets (sync state, history freshness, webhook delivery, versions) and the state vocabulary (connected, not_linked, linking with pairing code), which matters because there is no output schema. It does not mention rate limits or whether repeated polling is cheap.

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?

Three short sentences, front-loaded with what the tool reports and closing with the trigger condition. The telegraphic 'status (...), sync, how fresh the history is...' list is dense but readable; the ellipsis inside the status enumeration is the only sloppy element.

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?

With no output schema, the description must carry return-value semantics, and it partially does by naming the facets and status values. However, it never explains what 'versions' or 'webhook delivery' actually report, nor what happens when account_id is omitted, leaving real gaps for a tool whose whole purpose is inspection.

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

Parameters2/5

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

Two parameters at 50% schema coverage: include_picture is already documented in the schema (adds picture_url, expiring link), while account_id has no description anywhere. The phrase 'accounts lists every account, with default' only obliquely hints at default-account behavior when account_id is omitted, so the description fails to compensate for the undocumented parameter.

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?

The description names the resource (the account's connection state) and enumerates the concrete facets returned: status, sync, history freshness, webhook delivery, versions, and the accounts list. It is legible and distinguishable from siblings like get_media or list_chats, but the verb framing is compressed into 'Whether the account works' rather than a direct statement such as 'Returns connection status.'

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 condition: 'Call it on NOT_CONNECTED, NOT_LINKED or SYNC_IN_PROGRESS,' which tells the agent exactly when this tool is the right one. It stops short of stating when not to call it or naming an alternative, but the trigger is concrete enough to drive selection.

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