mcp-remnawave

squads_add_users

Add up to 1000 users to a squad in one asynchronous call. Provide squad UUID and user IDs to bulk assign members.

Instructions

Add specific users to an internal squad (1-1000 per call, async 202)

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": {
      "squadUuid": "<squadUuid>",
      "userIds": "<userIds>"
    },
    "name": "squads_add_users"
  }
}

Input Schema

Name	Required	Description	Default
`userIds`	Yes	Array of user numeric IDs to add
`squadUuid`	Yes	Squad UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the async nature ('async 202') and the per-call batch limit (1–1000), which is useful. However, it does not mention idempotency, permission requirements, or behavior on partial failure, leaving meaningful gaps for a mutation tool.

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 sentence with the core action front-loaded ('Add specific users to an internal squad') and constraints efficiently parenthesized. No redundant words; every element contributes to understanding the tool's behavior.

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 two-parameter tool with no nested objects and no output schema, the description covers the action, scope, batch size, and async response. It does not explain how to verify async completion or handle errors, but for its simplicity the definition is nearly complete.

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?

Both parameters are fully documented in the schema (squadUuid, userIds), giving 100% schema coverage. The description's '1–1000 per call' duplicates the schema's minItems/maxItems constraints without adding new meaning. Baseline 3 applies because the schema already carries the parameter semantics.

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 states a specific verb and resource: 'Add specific users to an internal squad.' The qualifier 'specific' differentiates it from sibling 'squads_add_all_users', and 'internal' contrasts with external squad tools. Clear, unambiguous, and distinguishable from siblings.

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 description implies use for a defined subset of users (1–1000 per call) as opposed to all users, but it never explicitly names alternatives like squads_add_all_users or squads_remove_users, nor does it state when not to use this tool. Usage context is implicit rather than explicit.

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

Deploy Server