mcp-remnawave

squads_get

Retrieve detailed information about a specific internal squad by providing its UUID, enabling quick access to squad configuration and status.

Instructions

Get a specific internal squad by UUID

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": {
      "uuid": "<uuid>"
    },
    "name": "squads_get"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes	Squad UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 10, 2026

TDQS

A3.6/5.0

Behavior2/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. 'Get' implies a read operation, but the description does not state what happens on not-found, whether authentication is required, or what the response shape looks like. For a no-annotation tool, more behavioral context is expected.

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?

The description is a single concise sentence with no unnecessary words. It front-loads the action, resource, and identifier type, making it immediately scannable and effective.

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?

This is a simple single-parameter getter with no nested objects or enums, so the description covers what is needed to invoke the tool correctly. The lack of an output schema is a minor gap, but the return value is reasonably inferable as a squad object. Overall, the definition is adequate for the tool's simplicity.

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%, and the uuid parameter is described as 'Squad UUID'. The description reinforces that the UUID identifies an internal squad but does not add format details, examples, or clarify whether this is a canonical UUID versus a short UUID. The schema already does the essential work here.

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 uses a specific verb ('Get') and identifies the resource ('specific internal squad') and the identifier mode ('by UUID'). This clearly distinguishes it from squads_list, which is for listing squads, and external_squads_get, which targets external squads.

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 context is clear: use this when you have a UUID and need one specific internal squad. However, the description does not explicitly mention alternatives or exclusions, such as 'use squads_list to browse all squads' or 'use external_squads_get for external squads', leaving some routing to inference.

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

Deploy Server