Skip to main content
Glama

Drop tournament no-shows

drop_tournament_no_shows
Destructive

Drops sealed entrants who have not checked in at a revealed solo Swiss tournament before the first round. If get_my_event returns a nonempty noShowIds list, confirm those players with the organizer before calling. 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>",
      "expectedUserIds": "<expectedUserIds>"
    },
    "name": "drop_tournament_no_shows"
  }
}

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.
expectedUserIdsYesExactly the organizer’s noShowIds from get_my_event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the danger is signaled structurally. The description adds genuinely useful context beyond that: the mcp:manage scope requirement and the organizer-confirmation step. However, it never says what happens to the dropped players (removed from the tournament entirely?) or whether the action is reversible, which is exactly the kind of detail a destructive operation should disclose.

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 sentences, zero waste, with the scope constraint front-loaded and the precondition following it. Nothing is padded or redundant.

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, permission-gated mutation with no output schema, the description covers the critical pieces: what it affects, the prerequisite data source, the human confirmation step, and the auth scope. It loses a point for leaving the post-call state and reversibility unstated, which matters given destructiveHint=true.

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 60%, so the baseline is 3. The one sentence about expectedUserIds ('Exactly the organizer's noShowIds from get_my_event') merely restates the schema's own description verbatim, and the token/analytics parameters get no attention in the description. No semantic value is added beyond the structured fields.

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 gives a specific verb (drops) and a precisely scoped resource: sealed entrants who have not checked in at a revealed solo Swiss tournament before the first round. That is much clearer than the title alone and implicitly separates it from check_in_tournament_entrant. It falls short of 5 only because the jargon (sealed, revealed, solo Swiss) is not unpacked for an agent unfamiliar with the domain.

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 states an explicit precondition tied to a named sibling: only call when get_my_event returns a nonempty noShowIds list, and confirm with the organizer first. This is clear when-to-use guidance. It stops short of 5 because it does not describe when not to use it, e.g. what to do if the list is empty or the tournament is not yet revealed.

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