Skip to main content
Glama

Withdraw from a tournament

withdraw_from_event
Destructive

Withdraws the signed-in player from a tournament. The entry and recorded results are kept. Confirm the tournament and withdrawal. 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": "withdraw_from_event"
  }
}

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.5/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 description earns credit for adding that "the entry and recorded results are kept" — a meaningful nuance that tells the agent this is a soft withdrawal rather than a purge of history. It also discloses the mcp:manage auth requirement. It stops short of saying whether the player may rejoin or how the event's capacity/roster is affected.

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, then the persistence behavior, then the permission requirement. Nothing is padded and no sentence is wasted.

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?

There is no output schema, so the description must carry what happens on success/failure, and it partially does by stating the entry and results are retained. Still, for a destructive mutation with four parameters and half of them undocumented, the description leaves an agent unsure which identifier to supply and what happens if the player is not entered or the event is in progress.

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 coverage is only 50%, so the description must compensate for the undocumented parameters, and it does not. Neither the required "token" nor the "eventToken" (presumably the tournament identifier) is explained, and "Confirm the tournament" is the only indirect hint that a tournament identifier is needed.

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 opens with a specific verb+resource pair: "Withdraws the signed-in player from a tournament," which tells an agent exactly what state change occurs and on whose behalf (the signed-in player, not an arbitrary entrant). It lacks any explicit contrast with nearby tools such as drop_tournament_no_shows or moderate_event_entrant, so sibling differentiation is only implied.

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" and "Confirm the tournament and withdrawal" give a scope prerequisite and a pre-call confirmation instruction, which is real usage context. However, there is no guidance on when to choose this over an organizer-side drop or a moderation tool, and no exclusions or failure conditions are 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