Skip to main content
Glama

turnale

by app.turnale

Generate draw

generate_draw
Destructive

Generate (or regenerate) the draw and schedule. This IS the start action: the first draw moves the tournament from setup to active and closes self-signup — when the organiser says "start the tournament", call this. The result includes rounds_text — SHOW it to the organiser as-is, in whatever language they are writing to you in (it is English already, so relay it unchanged unless they are writing something else) so they can check who plays whom — and the seed that produced the draw: preview first, then confirm with that SAME seed to apply exactly the previewed draw. Free until the first result is recorded; after that this DISCARDS recorded results and requires BOTH confirm: true and discard_results: true. If the organiser asks for a format that is not supported, offer to note it with record_feedback. Optional overrides adjust the format first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoDraw seed returned by the preview — pass it back with confirm: true to apply exactly the previewed draw. Omit for a fresh draw.
roundsNo
confirmNoOmit or false: return a preview of what would change. True: apply it.
seedingNo
request_idNoOptional idempotency id — retrying a call with the same id never applies it twice
group_countNo
tournament_keyYesThe tournament's organiser key (starts with tk_)
discard_resultsNoRequired (true) when results already exist — separate acknowledgement that this redraw destroys them
points_per_matchNo
advance_per_groupNo
third_place_matchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedYes
matchesYes
previewNoTrue when this is a preview — nothing was changed
summaryYesWhat happened, in one line
rounds_textYes
discarded_resultsYes

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses critical behaviors: it moves tournament state, closes self-signup, discards recorded results after first result, and requires an explicit discard acknowledgement. It also explains the preview/seed mechanism, adding rich context.

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 efficient; every sentence adds valuable information. It is front-loaded with the core action and then expands into usage details. No wasted words, though it could be slightly restructured for easier scanning.

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?

For a complex, destructive mutation tool, the description covers all essential flows: starting the tournament, previewing with seed, confirming, redrawing, handling existing results, and unsupported format feedback. The output schema exists and rounds_text is explicitly mentioned, making the tool's behavior fully understandable.

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 description adds meaning to key parameters (seed, confirm, discard_results) and explains the preview/confirm relationship. However, schema coverage is only 45%, and the description does not compensate for the many undocumented parameters like rounds, seeding, group_count, points_per_match, advance_per_group, and third_place_match. It partially compensates but leaves gaps.

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 with a specific verb+resource: 'Generate (or regenerate) the draw and schedule.' It also clearly differentiates the tool from siblings by describing it as 'the start action' that moves the tournament from setup to active and closes self-signup.

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?

Explicit when-to-use guidance is provided: call when the organiser says 'start the tournament'. It details the preview/confirm workflow, the condition for discarding results (requires both confirm:true and discard_results:true), and points to record_feedback as an alternative for unsupported formats.

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

All turnale toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Several tools serve overlapping purposes: get_pdf and get_pdf_link both return PDF artifacts, get_schedule and list_matches both provide match scheduling info, and get_results vs. get_standings can be confused for finished tournaments. However, the descriptions clarify the distinctions (embedded vs. link, upcoming vs. all matches, final vs. current standings), and roster-management tools are clearly separated by action.

Naming Consistency5/5

All 30 tools consistently use lowercase snake_case with a verb_noun pattern (e.g., create_tournament, record_results, withdraw_player). The only slight variation is the mix of get_* and list_* for read operations, but that's a common and predictable convention. There are no camelCase or inconsistent verb styles.

Tool Count2/5

With 30 tools, the server exceeds the 'too many' threshold of 25. While the domain is complex, this count is heavy and may overwhelm agents, especially since several tools could be consolidated (e.g., get_pdf/get_pdf_link, get_schedule/list_matches). A more streamlined set around 20 tools would be more appropriate.

Completeness5/5

The tool set provides comprehensive lifecycle coverage for tournament management: create/delete/end tournaments, manage players (add, remove, replace, withdraw, promote, update), generate draws, record results, handle doubles pairs, reschedule, retrieve standings/schedule/results, export/PDF, audit log, undo changes, and feedback. No major gaps are apparent for the stated purpose.

Resources