mcp-remnawave

external_squads_reorder

Reorder external squads by providing an ordered array of squad UUIDs to update their sequence.

Instructions

Reorder external squads

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": {
      "uuids": "<uuids>"
    },
    "name": "external_squads_reorder"
  }
}

Input Schema

Name	Required	Description	Default
`uuids`	Yes	Ordered array of squad UUIDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply states 'Reorder external squads' without explaining whether the provided UUID array replaces the entire order, what happens to omitted squads, or whether any validation occurs. This is a mutation operation, yet the description gives no clues about side effects or constraints.

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

Conciseness2/5

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

While the description is extremely concise with no fluff, it is under-specified. A one-phrase description like this is not just concise but lacking in necessary detail, similar to a placeholder. It does not front-load critical information beyond the basic action.

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 simple one-parameter tool, the description is still incomplete. It does not explain the concept of 'external squads', the semantics of the ordering, or any expected outcomes. Without an output schema or annotations, the minimal description leaves an agent with too many unknowns to confidently invoke it correctly.

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?

The input schema already provides a clear description for the single parameter: 'Ordered array of squad UUIDs' with 100% coverage. The tool description adds no additional meaning beyond that, so it aligns with the baseline of 3 for high schema coverage.

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 states a specific verb ('Reorder') and a specific resource ('external squads'), which distinguishes it from sibling reorder tools like squads_reorder, nodes_reorder, and hosts_reorder. However, it does not clarify what 'external squads' are or what the reordering affects (e.g., display order, priority), so some ambiguity remains.

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 guidance on when to use this tool versus alternatives such as squads_reorder or other reorder tools. The description provides no context about scenarios that would call for reordering external squads specifically, nor any exclusions or prerequisites.

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

Deploy Server