Whatify MCP Server

whatify_list_contacts

Search and filter contacts by phone, name, tag, or status. Retrieve a paginated list of contacts from your WhatsApp account.

Instructions

List/search contacts.

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

Input Schema

Name	Required	Description
`tag`	No
`name`	No
`phone`	No
`status`	No	active, inactive, blocked, or opted_out
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 14, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states 'list/search,' omitting behaviors like pagination (per_page parameter), filtering capabilities, or any side effects. No disclosure of rate limits or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at one phrase, but this brevity comes at the cost of completeness. It is front-loaded but lacks necessary details, making it minimally useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, no output schema, and no annotations, the description is vastly insufficient. It does not explain return values, pagination behavior, filtering logic, or any operational nuances, leaving the agent with inadequate context.

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?

Schema description coverage is only 20% (status parameter has a description). The tool description adds no explanation for parameters like tag, name, phone, or per_page, failing to compensate for the low schema coverage.

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 'List/search contacts' clearly indicates the verb-action (list/search) and the resource (contacts), distinguishing it from siblings like 'whatify_get_contact' (single retrieval) and 'whatify_create_contact' (creation). However, it lacks specificity about the combined functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'whatify_get_contact' for a single contact or other listing tools. There is no mention of prerequisites, filters, or use cases.

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

Deploy Server