WhatsApp MCP Stream

get_chat_by_contact

Read-onlyIdempotent

Resolve a contact by name or phone number to retrieve chat metadata, including message details and participant information.

Instructions

Resolve a contact by name or phone number and return the chat metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "get_chat_by_contact"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Name or phone number to resolve
`max_candidates`	No	Maximum number of matches to consider

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, indicating a safe read operation. The description does not add behavioral details beyond what annotations provide, such as rate limits or data freshness.

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?

The description is a single, front-loaded sentence with no wasted words, efficiently conveying the tool's purpose.

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 tool with two parameters and no output schema, the description is adequate. It could note that it returns chat metadata, but overall it is complete enough given annotations and schema.

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 input schema has 100% description coverage, so the schema already explains the parameters (query and max_candidates). The description does not add extra meaning or clarify parameter interactions beyond 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 clearly states the action (resolve a contact) and the resource (chat metadata), and distinguishes from siblings like get_chat_by_id or get_direct_chat_by_contact_number by specifying resolution by name or phone number.

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?

The description implies usage for resolving a contact by name/phone, but does not explicitly state when not to use it (e.g., when you have an ID, use get_chat_by_id) or provide alternatives among siblings.

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