Skip to main content
Glama

Read an entrant’s sealed roster

get_event_roster
Read-onlyIdempotent

Reads a sealed roster the signed-in player may see, by event token and entrant id from get_my_event. The site applies its rules for access before and after reveal. 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>",
      "userId": "<userId>"
    },
    "name": "get_event_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
userIdYes
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

B3.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses two things the annotations cannot: access is gated by the site's rules and differs before versus after reveal, and the call needs the mcp:read scope. It omits what a denial or pre-reveal redaction looks like in the response.

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?

Three short sentences with the resource and access condition front-loaded and no filler. The auth note is tacked on at the end but remains terse.

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 read-only lookup this covers the essentials: what it reads, whose data, and the access regime. The gaps are the ambiguous token/userId versus eventToken mapping and the absence of any note on failure or redacted results, which matter given there is no output schema.

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 description coverage is 40%, so the description needs to carry weight, but it only loosely maps 'event token and entrant id' to the actual required fields (token, userId) and never resolves whether eventToken is the same token or a distinct one. The two undocumented analytics parameters are also unaddressed.

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?

States a specific verb and resource ('Reads a sealed roster') plus the access scope ('the signed-in player may see'), which separates it from the public and personal roster siblings. It does not explicitly name a sibling, but the 'sealed' qualifier does differentiating work.

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?

Usage is implied: call it with an event token and entrant id sourced from get_my_event. It never states when to prefer this over get_my_roster or get_public_roster, nor what to do when access is denied, so the agent must infer the boundaries.

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