Skip to main content
Glama

Read a tournament or hidden-list game

get_my_event
Read-onlyIdempotent

Returns a tournament or hidden-list game as the signed-in player may see it: rules (format, size, points, what lists may break), dates, entrants with whether each sealed, your entry, Swiss rounds with your table and opponent (and at a team tournament each team meeting's revealed picks), standings once lists are revealed (and team standings, whose score is games won or victory points), your battles in it, and todo: what you still need to do. Organizers also see entrants’ check-in, noShowIds before the first solo Swiss round, and table results. Pass tableRound to inspect an earlier round’s tables. If a tracked battle has unknown status in a partial event, read it by token with get_public_battle. Before the reveal nobody's list is shown but your own name for it. Requires mcp:read.

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": "get_my_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.
tableRoundNoRound whose tables an organizer wants to inspect, defaulting to the current round.
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. Changed1 schema field changed
    • addedInput schema / properties / tableRound
      Added value: +{
      +  "description": "Round whose tables an organizer wants to inspect, defaulting to the current round.",
      +  "maximum": 64,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. 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"
      +}
  3. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already mark this read-only, idempotent and non-destructive, and the description adds role- and state-dependent behavior on top: organizers additionally see check-in, noShowIds before the first solo Swiss round, and table results, while non-organizers do not. It also discloses the reveal gating rule ('Before the reveal nobody's list is shown but your own name for it') and the required mcp:read scope — genuinely useful context not present in structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the purpose and then packaged as one very long sentence enumerating return contents, which makes it dense but hard to scan. The enumeration earns its place given there is no output schema, yet a short bulleted or clause-broken structure would communicate the same content far more efficiently.

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?

With no output schema, the description carries the burden of describing returns and it does so thoroughly, including standings scoring and team variants, plus the mcp:read prerequisite and reveal gating. Remaining gaps are minor — nothing about pagination, error behavior on an invalid token, or size limits for large events.

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 100%, so every parameter is already documented in the schema, including tableRound's default of the current round. The description adds only a light gloss — that tableRound serves an organizer inspecting an earlier round — and says nothing about llm_model or conversation_id beyond what the schema states. Baseline 3 is appropriate when the schema carries the load.

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 opening clause gives a specific verb and resource — 'Returns a tournament or hidden-list game as the signed-in player may see it' — and the subsequent enumeration makes clear this is a single-event read. It distinguishes itself from get_public_battle for the tracked-battle edge case, but does not clarify its relationship to other overlapping reads such as get_event_roster or list_my_events.

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 explicit routing: use tableRound to inspect an earlier round's tables, and read a tracked battle with unknown status via get_public_battle by token. It also states the token comes from list_my_events or an invite link. What it lacks is when NOT to use this tool versus the roster/list siblings, so it stops short of the 5 bar.

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