WhatsApp MCP Stream

run_group_audit

Read-onlyIdempotent

Analyze WhatsApp group memberships to identify overlapping members, members with no direct chat, and members not in your contacts.

Instructions

Run a combined group-membership audit (overlaps, no direct chat, not in 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": "run_group_audit"
  }
}

Input Schema

Name	Required	Description
`group_limit`	No	How many groups to scan
`refresh_group_info`	No	Fetch live group metadata before analysis
`overlap_min_shared_groups`	No	Threshold for overlap list
`min_shared_groups`	No	Threshold for no-direct-chat and not-in-contacts lists

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety is fully disclosed. The description does not contradict any annotation; it simply describes the combined audit operation, which is consistent with a read-only, idempotent call.

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?

A single 12-word sentence that is front-loaded and contains no fluff. Every part is essential for understanding the tool's purpose.

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

Completeness5/5

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

Given the lack of an output schema and high coverage in annotations and parameter descriptions, the description sufficiently explains the tool's function. It tells the agent what will be audited (overlaps, no direct chat, not in contacts) which is adequate for use.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The tool description adds context by naming the three audit types ('overlaps, no direct chat, not in contacts'), helping to conceptually link the parameters to these sub-audits, though it doesn't detail individual parameter behavior.

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 uses a specific verb 'Run' and a specific noun 'combined group-membership audit', listing three components: overlaps, no direct chat, not in contacts. This clearly distinguishes it from sibling tools like find_members_not_in_contacts and find_members_without_direct_chat.

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?

The description implies this tool runs a combined audit covering three areas, which differentiates it from more specific sibling tools. However, it does not explicitly state when to use this tool versus running the individual audits separately, and no exclusion criteria are mentioned.

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