Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Get the WhatsApp connection status

get_status
Read-onlyIdempotent

Check WhatsApp account status: connection, sync, history freshness, webhook delivery, and versions. Use when status is not connected, not linked, or sync in progress.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoAccount id

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
+}
  3. First observedv0.9.3

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about what the status includes and when to call it, but it does not disclose details like what the default account behavior is or what 'fresh' history means. It neither contradicts annotations nor adds much deeper behavioral richness.

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?

The description is compact, front-loaded with the core purpose, and the trigger condition is placed at the end as a natural action item. The enumeration of status facets is dense but each item earns its place; no filler sentences.

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 simple read-only tool with one optional parameter and no output schema, the description covers what the status includes and when to call it. The only real gap is that it never explicitly states what happens when account_id is omitted, though 'with default' hints at it.

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

Parameters3/5

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

The schema documents account_id at 100% coverage, so the description does not need to repeat it. The phrase 'accounts lists every account, with default' hints at default-account behavior for the optional parameter, but it is ambiguous and adds only marginal value over the schema.

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 clear verb+resource ('get status') and enumerates the specific facets it covers: connection state, sync, history freshness, webhook delivery, versions. This differentiates it from the chat/message-oriented siblings and leaves little ambiguity about what get_status reports.

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 explicitly gives conditional trigger conditions: 'Call it on NOT_CONNECTED, NOT_LINKED or SYNC_IN_PROGRESS.' It does not explicitly name sibling alternatives or exclusions, but the trigger guidance is concrete and actionable, so it is above average.

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