Skip to main content
Glama

Check in a tournament entrant

check_in_tournament_entrant
Destructive

An organizer marks an entrant from get_my_event as present or undoes their check-in before the first round is paired. 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>",
      "userId": "<userId>",
      "checkedIn": "<checkedIn>"
    },
    "name": "check_in_tournament_entrant"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
userIdYes
checkedInYes
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true. The description adds valuable non-annotation context: the auth scope needed and the pre-pairing deadline, plus the fact that the operation can be reversed. However, with destructiveHint=true it never explains whether existing pairing/roster state is affected or what happens if the deadline has passed.

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, front-loaded with the action and immediately followed by the prerequisite. Every clause carries information: role, entrant source, both boolean directions, timing constraint, and permission scope.

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?

For a 6-parameter mutation tool with no output schema and low schema coverage, the definition is competent but incomplete — it never clarifies eventToken (vs. token), nor what confirmation the caller receives. Annotations already cover the safety profile, which keeps this from being a larger gap.

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 only 33%, so the description must carry weight for token, userId, checkedIn, and eventToken. It successfully explains that checkedIn toggles present versus undo and implies userId selects an entrant from get_my_event, but token and eventToken remain entirely undefined in both schema and description.

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 states a specific verb and resource ('marks an entrant ... as present or undoes their check-in') and scopes the entrant source to get_my_event, so an agent can tell this apart from generic entrant tools. It stops short of naming near neighbors like check_in_event or moderate_event_entrant, so the differentiation is implied by the organizer/self-service framing rather than stated.

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 gives a concrete timing window ('before the first round is paired') and a permission prerequisite ('Requires mcp:manage'), which is real when-to-use context. There are no explicit exclusions or named alternatives, so an agent must infer that check_in_event handles a different (likely player-initiated) path.

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