Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

List the phone's address book

list_contacts
Read-onlyIdempotent

Retrieve paginated saved contacts from a WhatsApp account, including names, E.164 phone numbers, chat and contact IDs, and last direct-message time and direction; private entries excluded.

Instructions

The phone's address book on one account, a page at a time: saved name, phone (E.164), chat_id, contact_id, and when the last direct message was and its direction. No message words; #private people left out. address_book_synced false: not arrived yet.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
orderNorecent: latest direct chat first, then the rest in address book orderrecent
cursorNonext from the previous page
account_idNo

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. Addedv1.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding behavior they cannot express: results are paginated, message bodies are never returned, #private people are filtered out, and an address_book_synced=false state means the sync has not landed yet. The last point is a genuine precondition an agent could otherwise misread as an empty book.

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 resource and its returned fields are front-loaded, and no sentence is padding. The telegraphic fragments ('No message words') are terse to the point of being slightly cryptic, but they are information-dense rather than redundant.

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?

With no output schema, the description correctly takes on the burden of describing return fields, and it does so item by item. Combined with the pagination, privacy filtering, and sync caveats, an agent has enough to call this correctly; only paging termination and limit bounds are left implicit.

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?

Schema coverage is 50%: order and cursor are documented in the schema, while limit (default 100, max 500) and account_id are not. The description contributes 'one account' framing and 'a page at a time' pagination semantics, but says nothing about page size bounds or what cursor advancement looks like, so it only partly closes the gap.

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 a specific resource (the phone's address book for one account) and enumerates what each row carries: name, E.164 phone, chat_id, contact_id, and last DM timestamp plus direction. That is far more than the title restated. It stops short of explicitly distinguishing itself from the sibling find_contact, so an agent must infer that this is the bulk listing rather than the lookup.

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?

Usage is implied by 'a page at a time' and by the exclusion notes, which tell the agent this is a paged read of the whole book rather than a search. There is no explicit statement of when to prefer this over find_contact or list_chats, and no guidance on how to detect the final page.

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