turnale

Remove players

remove_player

Remove one or MANY players before any result is recorded (afterwards use withdraw_player or replace_player) — pass player_names to clear several in one call, never loop one-by-one. Regenerates an existing unlocked draw.

Input Schema

TableJSON Schema

Name	Required	Description
`request_id`	No	Optional idempotency id — retrying a call with the same id never applies it twice
`player_name`	No
`player_names`	No	Bulk removal — e.g. clearing mistaken placeholder names in one call
`tournament_key`	Yes	The tournament's organiser key (starts with tk_)

Output Schema

TableJSON Schema

Name	Required	Description
`preview`	No	True when this is a preview — nothing was changed
`removed`	Yes
`summary`	Yes	What happened, in one line
`promoted`	Yes	Waitlisted players who took the freed spots
`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#"

Changed2 schema fields changedJul 31, 2026

addedOutput schema / properties / promoted

Added value: +{
+  "description": "Waitlisted players who took the freed spots",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "players_total",
-  "removed",
-  "summary"
-]New value: +[
+  "players_total",
+  "removed",
+  "promoted",
+  "summary"
+]

First observedJul 29, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Discloses the side effect of regenerating an existing unlocked draw, which is not evident from the annotations or schema. Annotations only indicate non-read-only, and the description adds specific behavioral context about draw regeneration and timing constraints. Could be improved by clarifying behavior for locked draws or mixed param usage, but it goes beyond baseline.

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?

Two sentences, densely packed with essential information: action, timing, alternatives, batching, and side effects. No redundant words, and the most critical information is front-loaded.

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 that an output schema exists, the description focuses on what the tool does, when to use it, and its side effects. It covers the key scenarios: single removal, bulk removal, and timing constraints. The description is sufficiently complete for an agent to select and invoke the tool correctly.

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?

The schema describes 3 of 4 parameters (75% coverage), and the description adds meaning beyond this by instructing to use player_names for bulk removal and explicitly warning against one-by-one looping. The description does not explain the singular player_name parameter, but the schema's coverage partially compensates. Overall, it enhances parameter understanding.

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 begins with 'Remove one or MANY players' which clearly specifies the verb and resource. It also adds temporal context ('before any result is recorded') and distinguishes from sibling tools by mentioning alternatives (withdraw_player, replace_player), making the tool's unique purpose unambiguous.

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?

Explicitly states when to use this tool ('before any result is recorded') and when to use alternatives ('afterwards use withdraw_player or replace_player'). Provides additional guidance on batching ('never loop one-by-one'), which is practical and actionable.

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.