Skip to main content
Glama

Register

register
Destructive

Enter a house Sit & Go or a freeroll (tables lists them under tournaments): a Sit & Go's buy-in, its fee included, moves from your balance to escrow, and it starts when full; a freeroll is free, one entry a day. You play one table or Sit & Go at a time. A shadow enters the daily freeroll with its pass, and its prize waits for it to sign up.

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": "register"
  }
}

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

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

The description goes well beyond the annotations by disclosing that the buy-in (fee included) moves from balance to escrow, that the game starts only when full, and that freeroll entry is capped at one per day. That is substantive behavioral context for a destructiveHint=true mutation, though it omits what happens on failure (insufficient balance, table full, already registered).

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 tight sentences with the action and cost front-loaded, and no filler. The closing sentence about a shadow entering the daily freeroll with its pass is cryptic and reads as lore rather than actionable instruction, slightly diluting an otherwise efficient text.

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 money-moving, four-parameter mutation with no output schema, the description covers cost, escrow, timing, and entry limits, which is most of what an agent needs. The notable gap is outcome semantics: it never says what a successful or rejected registration looks like or how to recover from one.

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%, so every parameter, including key, shadow, and idempotency_key, is already documented in the schema itself. The description only re-explains that the tournament id comes from tables, adding little beyond the structured fields; baseline 3 applies.

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?

The description names a specific verb (enter/register) and specific resources (house Sit & Go, freeroll) and even resolves where to find the id ("tables lists them under tournaments"). It is clear what the tool does, though it does not explicitly distinguish itself from close siblings such as signup or sit_down.

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?

It supplies real preconditions: you play one table or Sit & Go at a time, a freeroll allows one entry a day, and a shadow must use its pass. However, it never names an alternative tool or says when NOT to call it, so the agent must infer the boundary with unregister, signup, or sit_down.

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