Skip to main content
Glama

Reveal sealed rosters

reveal_event_rosters
Destructive

Irreversibly reveals sealed rosters in a tournament or hidden-list game, where the signed-in player has permission. Ask for explicit confirmation to reveal now. 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>"
    },
    "name": "reveal_event_rosters"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
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.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's real contribution is the word "irreversibly" and the mcp:manage scope requirement, both of which add real information about consequences and auth. It does not say what the revealed data looks like afterward, whether other players are notified, or what the blast radius is, so it is not fully transparent for a destructive write.

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, front-loaded with the irreversible-action warning and ending with the hard permission requirement. No filler, though the confirmation sentence could be folded in more economically.

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 destructive, open-world operation with no output schema, the description covers confirmation and permissions but leaves the scope of the reveal undefined, including whether eventToken selects the event or whether all sealed rosters are revealed. An agent can act safely but not precisely.

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?

Only half the parameters have schema descriptions, and the two undocumented ones (token and eventToken) are exactly the ones that matter operationally. The description never explains that eventToken targets a specific event or what token represents, so it does not compensate for the coverage gap.

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?

"Irreversibly reveals sealed rosters in a tournament or hidden-list game" gives a specific verb plus resource and names the two game contexts where it applies. What it does not do is distinguish itself from the very close sibling unseal_event_roster, so an agent still has to guess which of the two to pick.

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 states the precondition for use (the signed-in player must have permission) and prescribes the interaction flow (ask for explicit confirmation before revealing now), which is strong guidance for a destructive action. It stops short of naming when to prefer unseal_event_roster or start_sealed_league instead, leaving the main ambiguity unresolved.

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