Skip to main content
Glama

Pair the next tournament round

pair_tournament_round
Destructive

A tournament organizer pairs the next Swiss round once each table from the previous round is finished. Confirm before publishing pairings. 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>"
    },
    "name": "pair_tournament_round"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
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.9/5.0
Behavior4/5

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

Annotations already flag destructive=true, openWorldHint=true and readOnlyHint=false; the description adds real value on top by disclosing the mcp:manage permission requirement and a confirm-before-publish step that matters for an irreversible, publicly visible action. It still doesn't say whether pairings can be undone or how the publishing step is triggered.

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, then the precondition, then the safety and auth constraints. No filler, though the confirmation instruction could be merged with the permission note.

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

Completeness4/5

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

For a destructive, open-world mutation with no output schema, the description covers the trigger condition, permission requirement and confirmation step. The main remaining gap is the undocumented eventToken and any description of what the pairing result looks like.

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?

Schema coverage is 50%, so token, llm_model and conversation_id are documented in the schema itself. The description adds no meaning for eventToken, which is the one parameter an agent must reason about to target the right tournament; coverage sits at the baseline-3 threshold.

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?

States a specific verb and resource: pairs the next Swiss round of a tournament. An agent can tell this creates pairings rather than reporting results or setting timers, though it doesn't explicitly name a sibling it is distinct from.

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?

Gives a clear precondition (every table from the previous round finished) and orchestrator guidance (confirm before publishing). It does not name alternatives or say what to do if a table is still open, but the when-to-use context is explicit.

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