turnale

Add players

add_players

Add players to the roster in bulk (parse pasted lists or spreadsheets yourself and send structured entries — never invent placeholder names; use signup mode when names aren't known yet). Duplicate names are rejected for disambiguation. If an unlocked draw exists it is regenerated automatically. Americano/mexicano take late arrivals even after results exist: americano rebuilds the rounds nobody has started, mexicano pairs them into the next round.

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": {
      "tournament_key": "<tournament_key>",
      "players": "<players>"
    },
    "name": "add_players"
  }
}

Input Schema

Name	Required	Description
`players`	Yes
`request_id`	No	Optional idempotency id — retrying a call with the same id never applies it twice
`tournament_key`	Yes	The tournament's organiser key (starts with tk_)

Output Schema

Name	Required	Description
`added`	Yes
`preview`	No	True when this is a preview — nothing was changed
`summary`	Yes	What happened, in one line
`players_total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 12, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed1 schema field changedJul 31, 2026
- removedInput schema / properties / players / items / properties / name / minLength
```
Removed value: -1
```
Changed2 schema fields changedJul 29, 2026
- addedInput schema / properties / players / items / properties / level / maximum
```
Added value: +10000
```
- addedInput schema / properties / players / items / properties / level / minimum
```
Added value: +-10000
```
First observedJul 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare non-read-only, non-destructive, closed-world, but the description adds important behavior: duplicate names are rejected for disambiguation, an unlocked draw is regenerated automatically, and late arrivals are handled differently in americano vs mexicano. That is substantial context beyond the annotations.

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?

The description is dense but front-loaded with the core action and bulk constraint. The americano/mexicano detail is somewhat long, but each sentence contributes specific 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?

An output schema exists, so return values needn't be explained. The description covers the mutation's side effects and edge cases well, though it could say more about failure modes when a duplicate is rejected or about signup mode mechanics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%. The description explains that callers must parse lists themselves and send structured entries, and it mentions placeholder names and signup mode, which clarifies the players array semantics. It does not add much about request_id or tournament_key beyond what the schema already says.

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 (add) and resource (players) and adds scope ('in bulk') plus mode nuance ('signup mode when names aren't known yet') that distinguishes it from single-player siblings like promote_player.

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

Usage Guidelines4/5

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

It gives clear usage context ('parse pasted lists or spreadsheets yourself', 'never invent placeholder names', 'use signup mode') but does not explicitly contrast with siblings such as update_player or replace_player or say when not to use this tool.

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

All turnale tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.