Skip to main content
Glama

Unregister

unregister
Destructive

Leave a Sit & Go before it starts: the whole buy-in comes back, fee included. Once it starts it plays to its end.

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": {
      "tournament": "<tournament>"
    },
    "name": "unregister"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.
shadowNoOnly without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.
tournamentYesThe Sit & Go's id, as tables lists it under tournaments.
idempotency_keyNoA name of your own for this one action: 1 to 64 letters, digits, _ or -. If you send the same action again under the same key, as after a lost reply, it is answered as the first was and happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / shadow
      Added value: +{
      +  "description": "Only without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.",
      +  "pattern": "^[A-Za-z0-9_-]{32}$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations flag destructiveHint=true and idempotentHint=false, and the description usefully offsets the destructive framing by declaring the outcome: the whole buy-in returns, fee included. It does not disclose what happens if the call is made after the start window (error vs. silent no-op), nor does it address the idempotency_key parameter, which sits awkwardly beside idempotentHint=false. Useful added context, but not a full behavioral picture.

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

Conciseness5/5

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

Two short sentences, zero filler, with the timing condition placed first so the agent reads the constraint before the consequence. Every clause earns its place.

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?

For a single-required-parameter mutation with annotations already covering the safety profile, the description supplies what matters: what it does, the timing window, and the refund outcome. The only meaningful gap is the behavior on a post-start call.

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 description coverage is 100%, including a detailed note that the tournament id is what 'tables' lists, so the schema carries parameter meaning on its own. The description adds no further parameter detail beyond implying the tournament must not have started yet.

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: leaving (unregistering from) a Sit & Go. That is plainly distinct from the sibling 'register' and from table-level actions like 'leave' or 'stand_up', although the description never names those siblings to reinforce the distinction.

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?

The when-to-use condition is explicit and front-loaded ('before it starts'), and the when-not case is stated too: once the tournament starts it plays to its end, so unregistering is no longer an option. It stops short of naming an alternative action to take after the start window closes, which keeps it from a 5.

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