Skip to main content
Glama

Make random teams

make_teams
Read-only

Use this when the user wants a random team generator: split a list of names into random teams or groups by number of teams or by team size, for a class, a game, a workshop, or a sports session. Team sizes differ by at most 1. Optional rules keep certain pairs apart or groups together. Returns each team's members. Does not balance by skill or rating (assignment is random), and is not for scheduling or seating charts. For fun, classroom, and team decisions only; not for lotteries, gambling, or prize draws that have legal requirements.

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": {
      "names": "<names>"
    },
    "name": "make_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesEveryone to split into teams, 2 to 200 names, e.g. ["Ana", "Ben", "Chloe", "Dev"].
team_sizeNoTarget people per team, e.g. 4. Makes as many teams as needed so no team is larger than this; sizes differ by at most 1.
keep_apartNoOptional pairs who must be on different teams, e.g. [["Ana", "Ben"], ["Chloe", "Dev"]].
team_countNoNumber of teams to make, a whole number from 2 up to the number of names, e.g. 3. Use this or team_size. Default 2.
team_namesNoOptional team names in order, e.g. ["Red", "Blue", "Green"]. Missing names default to Team 1, Team 2, ...
keep_togetherNoOptional groups who must be on the same team, e.g. [["Eli", "Fay"]].

Output Schema

NameRequiredDescriptionDefault
kindYes
sizesYes
teamsYes
peopleYes
keep_apartYes
team_countYes
keep_togetherYes
renamed_duplicatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: team sizes differ by at most 1, optional keep-apart and keep-together rules are respected, and assignment is random rather than skill-balanced. It also states that the tool returns each team's members and explicitly excludes scheduling, seating, and regulated prize-draw use cases.

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 front-loaded with the primary use case and then adds the key constraints and exclusions. Although dense, each sentence contributes useful selection or behavioral information.

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

Completeness5/5

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

Given the six parameters, complete schema descriptions, annotations, and an output schema, the description is complete enough for correct selection and invocation. It covers purpose, usage contexts, exclusions, key behavioral rules, and return shape.

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%, so the input schema already explains all six parameters with examples and constraints. The description reinforces the main modes and optional rules but does not add detailed parameter syntax or edge-case behavior beyond what the schema provides.

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: it splits a list of names into random teams or groups. It also names the supported inputs (number of teams or team size) and distinguishes the tool from unrelated random tools like lotteries, gambling, and prize draws.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use the tool: when the user wants a random team generator, and it lists valid contexts such as classes, games, workshops, and sports sessions. It also gives clear exclusions: it is not for scheduling, seating charts, lotteries, gambling, or legally regulated prize draws.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources