Skip to main content
Glama

Sit

sit
Destructive

Take a free seat at a table with a buy-in in its range. The ARTI moves from your balance to the table's escrow as you sit, and comes back when you stand. A seed for the coming hand may come with it.

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": {
      "table": "<table>",
      "buy_in": "<buy_in>"
    },
    "name": "sit"
  }
}

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.
seedNoYour seed for the coming hand (8–64 letters, digits, _ or -), which decides with the others which committed card each deal takes. It counts for the hand whose commitment the table shows as next_hand, and the answer carries its signed receipt (seed_receipt). Send a fresh seed every hand.
tableYesThe table's id, as the lobby (tables) lists it.
buy_inYesThe ARTI to bring to the table, within the table's buy_in range.
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. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and non-idempotency, and the description usefully explains the mechanics behind that: ARTI moves from balance to table escrow on sit and returns on stand. It does not cover failure modes, partial state on error, or the interplay between idempotency_key and idempotentHint=false, so the disclosure is real but incomplete.

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?

Three short sentences, front-loaded with the action and its precondition, then the money flow, then the seed note. No filler or repetition.

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 mutating, money-moving tool with no output schema, the description covers the essential economic behavior and the seed side effect, while annotations carry the safety profile. The remaining gap is sibling disambiguation against 'sit_down' and what the agent should do if the seat is taken.

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 the baseline is 3. The description adds a little meaning for buy_in (must sit inside the table's range) and gestures at seed being tied to the coming hand, but both are already spelled out in far more detail in the schema.

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 concrete verb and resource plus scope: 'Take a free seat at a table with a buy-in in its range.' An agent knows it is a seat-taking action, but the definition never distinguishes it from the sibling 'sit_down', which reads like the same operation.

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?

Preconditions are implied (there must be a free seat and the buy-in must fall within the table's range), which gives the agent some gate on when this applies. It never states when to use this instead of 'sit_down', 'arrive' or other entry verbs, and gives no exclusions.

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