Skip to main content
Glama

promote_participants

Promote participants to group admins in the Zappaz WhatsApp API by providing the group ID and participant list.

Instructions

Promove participantes a administradores de um grupo na Zappaz API

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": {
      "data": "<data>",
      "groupId": "<groupId>"
    },
    "name": "promote_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
groupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It implies a privilege-granting mutation but says nothing about required permissions, whether the change is reversible, partial-failure behavior for a batch of participants, or rate limits.

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?

A single compact sentence with the core action front-loaded, but its brevity is under-specification rather than efficiency given the 0% parameter coverage and missing mutation semantics.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and two entirely undocumented parameters, the description leaves too much unstated: permissions, error behavior, and the meaning of the 'data' array are all absent.

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 0%, so neither 'data' nor 'groupId' is documented anywhere. The description loosely implies the array holds participants and the ID names a group, but gives no format details (user IDs vs. phone numbers, batching limits) for the agent to build a correct call.

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?

States a specific verb and resource: promoting group participants to administrator status. It is clearly distinguishable from siblings like demote_participants, add_participants, and remove_participants, though it does not name them explicitly.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., the caller must already be an admin), and no routing to the inverse tool demote_participants. The agent must infer the usage context entirely.

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