Skip to main content
Glama

turnale

by app.turnale

Swap partners

swap_partners

Exchange two players' places. Fixed-pair doubles: swaps partners between two pairs permanently (name one player from each pair). Americano/mexicano: pass round to swap two players' places in ONE unplayed round — the courtside patch for a late arrival, an injury, or two friends who want a game together. One of them may be sitting that round, which is how you put a late arrival on court. Preview first, confirm to apply: the preview names any partnership or meeting the swap would repeat. Results already played never move.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roundNoAmericano/mexicano only: which round to patch. Omit to swap the next unplayed round.
confirmNoOmit or false: return a preview of what would change. True: apply it.
player_aYes
player_bYes
request_idNoOptional idempotency id — retrying a call with the same id never applies it twice
tournament_keyYesThe tournament's organiser key (starts with tk_)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairsNo
roundNo
previewNoTrue when this is a preview — nothing was changed
summaryYesWhat happened, in one line
repeats_meetingNo
repeats_partnershipNo

TDQS

A5/5.0
Behavior5/5

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

The description discloses that fixed-pair swaps are permanent, that Americano/mexicano swaps occur in exactly one unplayed round, and that the preview names any repeated partnership/meeting. This goes far beyond the annotations (readOnlyHint=false, destructiveHint=false), giving the agent a clear picture of the tool's behavior and side effects.

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?

Despite covering multiple formats and workflow details, the description stays tight and well-structured with colons and semicolons. Every sentence carries essential information with no redundancy or filler.

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?

It covers both tournament formats, the preview/confirm mechanism, edge cases like a sitting player, and the immutability of played results. Given the output schema exists, it appropriately omits return-value details, yet still gives the agent a complete mental model of when and how to invoke the tool.

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?

It adds meaning to 'round' (only for Americano/mexicano, omit for next unplayed round) and 'confirm' (preview vs apply), which are not fully explained in the schema. It also implicitly clarifies that player_a and player_b represent one player from each pair in fixed-pair mode. With 67% schema coverage, this fills the gap effectively.

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 'Exchange two players' places' and immediately distinguishes between fixed-pair doubles (swaps partners permanently) and Americano/mexicano (swaps places in one unplayed round). This specific verb+resource+scope clearly differentiates it from sibling tools like replace_player or set_pairs.

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 frames the tool as the 'courtside patch for a late arrival, an injury, or two friends who want a game together,' and clarifies both format-specific usage and the constraint that 'Results already played never move.' It also instructs to 'Preview first, confirm to apply' for a safe workflow.

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