Skip to main content
Glama

Limits

limits
Destructive

Your limits on what you lose, and a cool-off: read them, or set them. show: Your own loss limits and cool-off, shown to you alone: for each UTC day, week and month, the limit on your net poker losses, what you've lost so far, what is left and when it resets, and any change still waiting. For members. set: Set limits on your net poker losses (daily, weekly, monthly, in whole ARTI; null removes one) and a cool-off from the tables (24h, 7d or 30d). A lower limit holds at once; a higher one, or none, only after a wait; a cool-off can't be shortened. A buy-in or Sit & Go entry past a limit is refused, and every one during a cool-off. For members.

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": {
      "action": "<action>"
    },
    "name": "limits"
  }
}

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.
dailyNoYour daily limit on net poker losses, in whole ARTI; null removes it, and leaving it out leaves it as it is. A lower limit holds at once; a higher one, or none, only after a wait (the note says how long).
actionYesWhat to do: show, set.
weeklyNoYour weekly limit on net poker losses, in whole ARTI; null removes it, and leaving it out leaves it as it is. A lower limit holds at once; a higher one, or none, only after a wait (the note says how long).
monthlyNoYour monthly limit on net poker losses, in whole ARTI; null removes it, and leaving it out leaves it as it is. A lower limit holds at once; a higher one, or none, only after a wait (the note says how long).
cool_offNoA break from the tables, from now: 24h, 7d or 30d. Until it ends you can't sit, register or buy in, freerolls included; a seat or entry already taken plays on, and you can unregister from a Sit & Go not yet started. It can't be shortened once set.
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. Changed7 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
      +  "description": "What to do: show, set.",
      +  "enum": [
      +    "show",
      +    "set"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / cool_off
      Added value: +{
      +  "description": "A break from the tables, from now: 24h, 7d or 30d. Until it ends you can't sit, register or buy in, freerolls included; a seat or entry already taken plays on, and you can unregister from a Sit & Go not yet started. It can't be shortened once set.",
      +  "enum": [
      +    "24h",
      +    "7d",
      +    "30d"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / daily
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1000000000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Your daily limit on net poker losses, in whole ARTI; null removes it, and leaving it out leaves it as it is. A lower limit holds at once; a higher one, or none, only after a wait (the note says how long)."
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "A 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.",
      +  "pattern": "^[A-Za-z0-9_-]{1,64}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / monthly
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1000000000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Your monthly limit on net poker losses, in whole ARTI; null removes it, and leaving it out leaves it as it is. A lower limit holds at once; a higher one, or none, only after a wait (the note says how long)."
      +}
    • addedInput schema / properties / weekly
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1000000000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Your weekly limit on net poker losses, in whole ARTI; null removes it, and leaving it out leaves it as it is. A lower limit holds at once; a higher one, or none, only after a wait (the note says how long)."
      +}
    • addedInput schema / required
      Added value: +[
      +  "action"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only supply the safety profile (destructiveHint=true, idempotentHint=false); the description adds substantial behavioral context beyond them: a lower limit takes effect at once while a higher one or removal waits, a cool-off cannot be shortened, and existing seats or entries keep playing while new ones are blocked (including freerolls), with unregistering allowed for a not-yet-started Sit & Go. Those are exactly the irreversible-effect details an agent needs before a destructive set.

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?

The definition is front-loaded with a one-line summary followed by clearly labeled 'show:' and 'set:' blocks, so an agent can scan to the relevant mode. It is somewhat dense and run-on with colon/semicolon chains, and the 'lower limit holds at once' sentence is repeated across the description and three parameter descriptions, but nothing is superfluous enough to impede selection.

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 7-parameter mutation tool with no output schema, the description usefully enumerates what show returns (per-day/week/month limit, lost so far, remaining, reset time, pending change) and what set enforces. The only gaps are that it says nothing about what set itself returns (the 'note' is only alluded to) and leaves key/idempotency handling entirely to the schema.

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 daily/weekly/monthly units, the null-removes semantics, and the cool_off enum are already fully documented in the schema. The description restates the same 'lower holds at once / higher after a wait' rule and the ARTI unit and 24h/7d/30d values without adding new syntax or format meaning, so the 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 resource (net poker loss limits per UTC day/week/month plus a cool-off) and the two operations (show/set), so it is clearly distinguishable from table-action siblings like sit, register, or unregister. The opening phrase 'what you lose' is slightly indirect and only resolved to 'net poker losses' in the set section, which keeps it from a 5.

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 two modes are spelled out with their own sections, giving clear routing between reading and mutating: 'show: Your own loss limits...' and 'set: Set limits on...'. It also explains the consequence condition — a buy-in or Sit & Go entry past a limit is refused, and every one during a cool-off — which tells an agent when this state matters relative to sit/register, though it never explicitly names those siblings as alternatives.

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