Skip to main content
Glama

Swap players between tournament tables

swap_tournament_table_seats
Destructive

An organizer swaps two entrants in the current Swiss round. Use the round, table numbers and ordered player ids from get_my_event. Confirm the affected tables before calling. Requires mcp:manage.

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": {
      "token": "<token>",
      "players": "<players>",
      "round": "<round>",
      "tables": "<tables>"
    },
    "name": "swap_tournament_table_seats"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundYesThe current Swiss round from get_my_event.
tokenYes
tablesYesThe table numbers of the two players, in the same order as players.
playersYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
eventTokenNo
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds real context beyond them: the required mcp:manage scope and the instruction to verify the affected tables first. It does not explain whether the swap can be undone or what happens to pairing state afterwards.

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?

Three short sentences, front-loaded with the action and followed by prerequisites in priority order. Every sentence carries information; the only cost is that the terseness leaves behavioral questions unanswered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, 7-parameter mutation with no output schema, the description covers the action, input source, a safety confirmation, and auth scope. It omits post-swap effects, error conditions, and whether the round must currently be in progress, which leaves gaps for a destructive operation.

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?

With schema description coverage at 57%, the description usefully clarifies provenance and ordering for round, tables and players (from get_my_event, same order). It says nothing about token, eventToken, llm_model or conversation_id, so the undocumented parameters remain unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (swaps) and resource (two entrants in the current Swiss round), which is concrete enough to distinguish it from siblings like pair_tournament_round or report_tournament_table. It does not explicitly name an alternative tool, so it stops short of a 5.

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?

"Use the round, table numbers and ordered player ids from get_my_event" gives an explicit source of truth for inputs, and "Confirm the affected tables before calling" adds a prerequisite step. There is no statement of when this should not be used or which sibling to prefer instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources