Skip to main content
Glama

Create, join or leave a tournament team

set_tournament_team
Destructive

For team Swiss, send a name to start a team, a squadId to join a team, or null to leave. Read team ids with get_my_event. 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>",
      "squad": "<squad>"
    },
    "name": "set_tournament_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
squadYes
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

A4.4/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, so the safety profile is partly covered. The description adds genuinely new context: the required 'mcp:manage' auth scope and the fact that passing null performs the destructive leave action. It does not say what happens to a team or membership when you leave, which would complete the picture.

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?

Two tight sentences: the scope and the tri-modal input contract come first, the dependency on get_my_event and the permission requirement follow. No filler, nothing redundant with the schema.

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 5-parameter mutation with no output schema, the description covers the operation set, the prerequisite lookup, and the auth scope. Gaps remain around what a leave does to existing memberships and how eventToken relates to token, which matter for a destructive tool.

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

Parameters4/5

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

Schema coverage is 40%, but the description fully compensates for the one ambiguous parameter by explaining the three anyOf variants of `squad` (name / squadId / null) and their intent. The remaining parameters (token, eventToken, the analytics fields) are not explained beyond their schema text, and the token vs eventToken distinction stays unclear.

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 names a specific resource (tournament team) and spells out three distinct operations mapped to input shapes: a name starts a team, a squadId joins one, null leaves. This lets an agent distinguish create/join/leave intent without opening the schema, and it names get_my_event as the reader for team ids.

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?

It scopes usage to 'team Swiss' and gives an explicit prerequisite step ('Read team ids with get_my_event'), which is real routing guidance. It does not state explicit when-not conditions or name an alternative for non-team-Swiss formats, so it falls just short of complete.

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