Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a WhatsApp group

create_group

Create a WhatsApp group with a given name and participant IDs; the linked account becomes the owner, and each participant returns a status (ok, invite needed, or failed).

Instructions

Create a group with the given name and participants; the linked account becomes the owner. Each participant comes back with a status: ok, invite_needed (their privacy settings require an invite link) or failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGroup name
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.
participant_idsYesChat ids or phone numbers to add (1-256)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.9.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, and openWorld=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the per-participant status vocabulary (ok, invite_needed, failed) tells the agent to expect partial success rather than all-or-nothing.

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 with no filler; the core action and required inputs come first, and the return-status detail is efficiently packed into the second sentence.

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 3-parameter mutation tool with no output schema, the description covers the action, required inputs, ownership effect, and return statuses. It stops short of explaining failure handling (e.g., what happens if every participant fails) or limits, but the essentials are present.

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 description coverage is 100%, so the schema already documents name, account_id, and participant_ids with constraints and defaults. The description only restates 'name and participants' and adds no format or resolution detail beyond the schema, so baseline 3 applies.

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 ('Create a group'), names the required inputs ('given name and participants'), and adds the ownership outcome ('the linked account becomes the owner'), which cleanly separates it from read-oriented siblings like get_group_info and manage_group.

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 creation context is implied by the verb, but there is no guidance on when to use this versus manage_group, nor any prerequisites (e.g., the account must be linked) or exclusions. Adequate but leaves the agent to infer routing.

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

Deploy Server

Other Tools