Skip to main content
Glama

Create a tournament

create_tournament

Creates a tournament using the chosen format, roster limits, listing, admission and schedule. Confirm those choices with the organizer. 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": {
      "name": "<name>",
      "visibility": "<visibility>",
      "admission": "<admission>"
    },
    "name": "create_tournament"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
teamsNo
formatNo1v1
roundsNo
scheduleNo
admissionYes
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.
allowancesNo
allyPointsNo
ownerPlaysNo
soloPointsNo
visibilityYes
descriptionNo
playerLimitNo
rosterLimitNo
pointsBudgetNo
sharedPointsNo
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.
clockLimitMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is covered. The description adds meaningful context beyond that: the manage scope requirement and the organizer-confirmation step. It says nothing about what happens with omitted optional parameters, defaults that will be applied, or failure behavior for a 19-parameter creation with nested schedule and teams objects.

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?

Two short sentences, front-loaded with the action and followed by the prerequisite and confirmation step; no filler. It is efficient, though the terseness is arguably under-specification given the schema's complexity rather than excess.

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

Completeness2/5

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

With 19 parameters, 11% schema description coverage, nested objects (teams, schedule), three enum families, and no output schema, an agent needs far more than two sentences to call this correctly. The description supplies only the auth scope and a confirmation ritual, leaving the bulk of configuration semantics undocumented.

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

Parameters2/5

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

Schema description coverage is only 11% across 19 parameters, so the description must carry the semantic burden and largely does not. It gestures at format, roster limits, listing, admission, and schedule, but leaves most parameters — teams, rounds, allowances, pointsBudget, soloPoints/allyPoints, ownerPlays, sharedPoints, playerLimit, clockLimitMinutes, llm_model, conversation_id — with no explanation of their interaction or defaults.

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 ("Creates a tournament") and enumerates the dimensions configured by the call: format, roster limits, listing, admission, and schedule. It does not, however, distinguish this from sibling creation tools such as create_battle or create_group, so the agent gets no explicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Requires mcp:manage" gives a concrete authorization prerequisite and "Confirm those choices with the organizer" gives a workflow precondition, which is real usage guidance. But there is no statement of when not to use it or which sibling to pick for alternative creation scenarios, so the guidance is implied rather than 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