Skip to main content
Glama

demote_participants

Demote group administrators to regular members in a Zappaz WhatsApp group using the group ID and participant data.

Instructions

Rebaixa participantes de administradores a membros 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": "demote_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
groupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 behavioral burden. It does disclose the state transition (admin → member), which is genuinely useful, but says nothing about required permissions, whether the change is reversible, what happens to invalid or non-admin participant IDs, or whether the operation is partial-failure tolerant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the resource and transformation front-loaded. No filler, though the terseness comes at the cost of missing detail rather than being optimally structured.

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 zero annotation coverage, no output schema, and 0% parameter documentation, a single sentence is insufficient. An agent lacks the permission, error, and parameter-format context needed to invoke it confidently.

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% for two required parameters. The description's mention of 'participants' and 'grupo' loosely hints that data holds participant identifiers and groupId targets a group, but it never clarifies that data is an array of user IDs or what format groupId takes.

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?

The description gives a specific verb (demote) plus resource (participants) and the exact state transition — from administrators to group members. An agent can distinguish it from promote_participants by the direction of the change, though no sibling is named 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 prerequisites, and no mention of alternatives or exclusions. The agent must infer that this is the inverse of promote_participants entirely on its own.

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