Local MCP

WhatsApp Create Group

whatsapp_create_group

Destructive

Creates a WhatsApp group and adds the given participants. This NOTIFIES everyone you add and cannot be undone if the participant list is wrong, so it is a write operation: the first call (confirm=false) returns a preview of the name + participants without creating anything; set confirm=true to actually create. Resolve numbers first with whatsapp_search_contacts.

Input Schema

Name	Required	Description
`name`	Yes	Group name
`account`	No	Which linked WhatsApp account to use: its label or id from whatsapp_list_accounts. Leave it out to use the default account.
`confirm`	No	Must be true to actually create. Without it, returns a preview.
`remember`	No	With confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.
`participants`	Yes	Phone numbers (+E164) or JIDs to add

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / remember

Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 10, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which linked WhatsApp account to use: its label or id from whatsapp_list_accounts. Leave it out to use the default account.",
+  "type": "string"
+}

AddedSep 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds material context the annotations cannot convey: added participants are notified, mistakes are irreversible, and the call is two-phase with a safe preview path. That is real behavioral disclosure beyond the structured fields.

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?

Two sentences, front-loaded with the effect (creates group, notifies people, irreversible) before the procedural detail. Every clause carries information; none is filler.

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?

For a destructive, open-world write tool with an output schema and 100% parameter documentation, the description covers the risk, the confirmation protocol, and the prerequisite lookup. Nothing an agent needs to invoke it safely is missing.

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 coverage is 100%, so the baseline is 3; the description earns above baseline by explaining the confirm parameter's preview-vs-create semantics in workflow terms and by stating that participants must be resolved phone numbers or JIDs via whatsapp_search_contacts. It does not cover account or remember, but those are fully documented in 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?

States a specific verb and resource ("Creates a WhatsApp group and adds the given participants") and implicitly separates itself from read-only siblings like whatsapp_list_groups and whatsapp_group_info. An agent can tell immediately this is the group-creation tool.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: call with confirm=false for a preview, confirm=true to actually create, and resolve numbers first with whatsapp_search_contacts. It names the sibling tool to use as a prerequisite, which is exactly the routing information an agent needs.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.