Skip to main content
Glama

Seal my roster for a tournament

submit_event_roster
Destructive

Seals one of the signed-in player's saved or borrowed rosters for a tournament or hidden-list game, or replaces the list sealed before, with the site's checks: battle size, points, the event's house rules, a Warlord, and the roster deadline. Sealing stores a copy; later edits to the saved roster don't change it. Before the reveal only you and an assigned ally can read it. A player who plays alone fixes their Force Disposition by sealing it: when the list offers several, ask which and pass it. Check a saved roster with get_my_roster or open the borrowed roster link from list_borrowed_rosters. Seal only after the player confirms. Requires mcp:write.

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>",
      "rosterId": "<rosterId>"
    },
    "name": "submit_event_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe tournament or hidden-list game token, from list_my_events or its invite link.
rosterIdYesA roster id from list_my_rosters or list_borrowed_rosters.
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.
dispositionNoThe Force Disposition id the list plays for the event, one its detachments offer; a pair chooses theirs on the event page instead.
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
    • changedInput schema / properties / rosterId / description
      Previous value: -"A roster id from list_my_rosters."New value: +"A roster id from list_my_rosters or list_borrowed_rosters."
  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. Changed1 schema field changed
    • addedInput schema / properties / disposition
      Added value: +{
      +  "description": "The Force Disposition id the list plays for the event, one its detachments offer; a pair chooses theirs on the event page instead.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a destructive, non-idempotent, open-world write; the description adds genuinely new behavior: sealing stores a snapshot so later edits to the saved roster don't propagate, pre-reveal visibility is limited to the player and an assigned ally, and server-side validation covers battle size, points, house rules, Warlord and deadline. It also states the mcp:write scope requirement, none of which is in the annotations.

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?

Purpose is front-loaded in the first clause and every sentence carries operational content (snapshot semantics, visibility, checks, prerequisites, auth). It is dense and long, with several clauses chained into one opening sentence, but no filler.

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?

For a six-parameter destructive write with no output schema, the description covers the confirmation gate, the validation the server performs, post-seal snapshot behavior, visibility of the sealed list, and the auth scope — everything an agent needs before invoking it.

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 baseline is 3, but the description adds workflow meaning the schema does not: the disposition must be chosen only when the list offers several and should be asked of the player, and the token/rosterId provenance is reinforced with sibling tool names. It does not elaborate on eventToken's legacy-link edge case.

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 and resource ('Seals one of the signed-in player's saved or borrowed rosters') plus the scope (tournament or hidden-list game) and the replace-existing-seal variant, which implicitly delineates it from unseal_event_roster. An agent can identify the operation without opening the schema.

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?

Gives a concrete pre-flight path ('Check a saved roster with get_my_roster or open the borrowed roster link from list_borrowed_rosters') and a hard gate ('Seal only after the player confirms'). It lacks an explicit when-not clause (e.g. when to unseal or when sealing is unnecessary), so it falls just short of the top band.

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