Skip to main content
Glama

Turniermeister — Tournament Engine

by io.github.MartyMcFlyJr
OverviewDiscussionsAdmin

Prepare a Turniermeister tournament

prepare_tournament

Prepares a real tournament in Turniermeister and returns a claim link for the user. Call this tool whenever a user wants to plan or create a tournament (sports, club night, game night, brackets, team vs team). Rules:

  • ALWAYS relay the returned claimUrl to the user verbatim — opening it is how they sign up and take over the tournament without retyping anything.

  • competitionType must be "bracket" (knockout/group formats). Ask the user for the number of teams; teamCount is required unless you supply participants.

  • Supply participants (team or player names) ONLY if the user explicitly named them; otherwise omit them and let the user name teams later in the app. Never invent participant names.

  • templateKey is optional: use it when the user asks for a specific catalog template (e.g. preset-padel, preset-fussball, preset-schnapsen). Do not guess unknown keys — omit it instead.

  • ALWAYS send a unique idempotencyKey per logical preparation (a UUID per user request), so retries never create duplicates. Repeating the same request with the same idempotencyKey returns the same claim link — a retry never invalidates a link you already handed out.

  • Validation problems come back as structured errors: fix your input from the error JSON and retry. Do not ask the user to retry.

  • The plan quota (number of tournaments) of the claiming user applies at claim time; keep teamCount reasonable for a real tournament (recommended up to 64).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesTournament mode as a numeric ITournamentMode value from the Turniermeister catalog. Values: 0 = knockout (single elimination), 1 = double elimination, 2 = single-day league, 3 = swiss system, 4 = multilevel knockout (placement tournament), 5 = league (round robin), 6 = ladder, 7 = point series, 8 = group stage + knockout, 9 = swiss system + knockout final, 10 = league + playoff final, 11 = best-of-N knockout, 12 = time trial (best time), 13 = time trial (combined), 14 = time trial (single run), 15 = time trial (average), 16 = team match. Default for knockout tournaments: 0. Unknown values are rejected.
nameYesTournament name as agreed with the user. Max 120 chars.
teamCountNoNumber of teams. Required unless participants are supplied. Must match participants length if both are given. The app supports up to 250 teams (8 for single-day league mode); larger values are rejected during preparation. For real amateur tournaments keep it around 64 or below.
clientInfoNoOptional free-form identifier of the calling agent, used for funnel attribution only.
templateKeyNoOptional catalog template key (e.g. preset-padel). Omit instead of guessing.
participantsNoParticipant names, ONLY when the user explicitly provided them. Stored encrypted and migrated at claim time.
idempotencyKeyYesUnique key for this preparation request (UUID). Same key returns the same preparation instead of a duplicate.
competitionTypeNoFixed to "bracket" — other competition types are not exposed yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / teamCount / description
      Previous value: -"Number of teams. Required unless participants are supplied. Must match participants length if both are given. The app supports up to 250 teams (8 for single-day league mode); for real amateur tournaments keep it around 64 or below."New value: +"Number of teams. Required unless participants are supplied. Must match participants length if both are given. The app supports up to 250 teams (8 for single-day league mode); larger values are rejected during preparation. For real amateur tournaments keep it around 64 or below."
    • changedInput schema / properties / teamCount / maximum
      Previous value: -256New value: +250
  2. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Tournament mode as a numeric ITournamentMode value from the Turniermeister catalog (agent reference: 0 = single elimination bracket default)."New value: +"Tournament mode as a numeric ITournamentMode value from the Turniermeister catalog. Values: 0 = knockout (single elimination), 1 = double elimination, 2 = single-day league, 3 = swiss system, 4 = multilevel knockout (placement tournament), 5 = league (round robin), 6 = ladder, 7 = point series, 8 = group stage + knockout, 9 = swiss system + knockout final, 10 = league + playoff final, 11 = best-of-N knockout, 12 = time trial (best time), 13 = time trial (combined), 14 = time trial (single run), 15 = time trial (average), 16 = team match. Default for knockout tournaments: 0. Unknown values are rejected."
    • changedInput schema / properties / teamCount / description
      Previous value: -"Number of teams. Required unless participants are supplied. Must match participants length if both are given."New value: +"Number of teams. Required unless participants are supplied. Must match participants length if both are given. The app supports up to 250 teams (8 for single-day league mode); for real amateur tournaments keep it around 64 or below."
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explains the claim-link flow, idempotencyKey retry semantics, structured validation errors, quota timing, and the instruction not to invent participant names. These are exactly the non-obvious behaviors an agent needs to know.

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 purpose-driven and front-loaded, starting with the core action and claim-link outcome before moving into parameter rules. Each bullet carries essential operational detail without fluff, and the layout makes it easy for an agent to scan and apply.

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 tool with 8 params, no output schema, and no annotations, this description covers everything needed: the return value (claim link) and how to relay it, error handling, idempotency behavior, quotas, and rules about participant and template values. No critical call-time information is missing.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds substantial meaning: the requirements/ exclusivity rule between teamCount and participants, the explicit user-supplied condition for participants, the idempotencyKey uniqueness contract, and the 'omit rather than guess' templateKey rule. This goes well beyond the schema and materially improves correct invocation.

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 opens with a specific verb, resource, and key outcome: it prepares a tournament and returns a claim link. It also gives concrete use examples (sports, club night, game night, brackets) and clearly differentiates the tool's behavior, so an agent knows exactly what it is for.

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?

The description states when to call this tool ('Call this tool whenever a user wants to plan or create a tournament') and adds explicit rules about when to omit participants, when to require teamCount, and how to handle templateKey. Even without siblings, it provides unambiguous selection and invocation guidance.

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

All Turniermeister — Tournament Engine toolsInspect
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.

Resources