Skip to main content
Glama

Join a tournament or hidden-list game

join_event
Destructive

Enters the signed-in player in a tournament by its token, as its invite link does, or in a hidden-list game of a group they belong to. A tournament whose organizer approves each player answers pending until they let you in. Closed once lists are revealed or the roster deadline passes. Requires mcp:write.

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": "join_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe tournament or hidden-list game token, from list_my_events or its invite link.
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.
eventTokenNoeventToken from list_my_events; only an old link needs it.
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. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare a non-readonly, destructive, non-idempotent, open-world write, and the description adds real context beyond that: the pending-approval outcome, the two closure conditions, and the required mcp:write scope. It does not explain what exactly is 'destructive' about a join (e.g., that it consumes a seat or cannot be undone), which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action and the token source before moving to outcomes and prerequisites. No filler or repeated phrasing.

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?

Covers the essentials for a write tool with no output schema: what it does, auth scope, pending state, and failure conditions. It stops short of describing the response (e.g., a status/roster object) or idempotency behavior on repeat calls, which an agent might want.

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 description coverage is 100%, so each of the four parameters is already documented, and the description only restates that a token identifies the tournament or hidden-list game. It adds no new meaning for eventToken, llm_model, or conversation_id, so the baseline 3 applies.

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?

States a specific verb and two precise resources: entering the signed-in player in a tournament by token, or in a hidden-list game of a group they belong to. The scope wording ('hidden-list game of a group they belong to') implicitly separates it from join_group and join_league, so an agent can route without opening the schema.

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 concrete usage context: the token comes from the invite link, organizer-approved tournaments leave the player pending, and joining is impossible once lists are revealed or the roster deadline passes. It does not explicitly name sibling alternatives like join_group or join_league, so the exclusion is inferred rather than stated.

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