Skip to main content
Glama

List my groups and tournaments

list_my_events
Read-onlyIdempotent

Lists the signed-in player's groups, tournaments and hidden-list games (a group's game where everyone seals a list in secret before the reveal), each with its token, url, dates and your place in it: membership, entry status, whether you sealed a list, and the size you seal at. Pass includeOpen to also list public groups and tournaments you could join. Read one with get_my_group or get_my_event. Requires mcp:read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
includeOpenNoAlso list public groups and tournaments you are not in.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context the annotations cannot: the auth scope requirement and a detailed account of the returned membership/entry/seal state. It stops short of mentioning pagination or result-size limits, which would have earned 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.

Conciseness4/5

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

Front-loaded with the core verb and resources, then the optional flag, then the read-alternatives and auth note — a sensible ordering with no filler. The first sentence is dense with parenthetical definition and a field list, which costs a little readability but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the return-value burden and does so thoroughly: token, url, dates, your place, membership, entry status, sealed-list state, seal size. Combined with the auth requirement and the sibling routing, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for includeOpen by framing it as "public groups and tournaments you could join" — a joinability nuance the schema's "you are not in" does not convey. The analytics parameters (llm_model, conversation_id) are left to the schema, which is acceptable since they are self-documented.

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 (lists) and three concrete resources (groups, tournaments, hidden-list games), and even defines the unusual one: "a group's game where everyone seals a list in secret before the reveal." It also enumerates the per-item fields returned, so an agent knows exactly what it gets back without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use includeOpen to widen the list to public groups/tournaments you could join, and use get_my_group or get_my_event to read a single item. It also states the prerequisite ("Requires mcp:read"), so the when-to-use, when-not-to-use and access conditions are all present.

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