Skip to main content
Glama

Act

act
Destructive

Make your move when it is your turn: fold, check, call, or bet or raise with amount (your whole bet for the round). The clock checks or folds for you after to_act.deadline. 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>",
      "hand": "<hand>",
      "moves": "<moves>",
      "action": "<action>"
    },
    "name": "act"
  }
}

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.
handYesThe hand you are acting in, as table shows it (hand).
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.
movesYesThe moves made in that hand so far, as table shows it (moves): your move answers that position, and is refused if the hand has moved on, so a late move never lands in the wrong spot.
tableYesThe table's id, as the lobby (tables) lists it.
actionYesfold, check, call, or bet or raise with amount: your whole bet for the round ("raise to"), within to_act.raise.
amountNoWith bet or raise: your whole bet for the round.
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.
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?

The annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered. The description adds deadline behavior and optional seed inclusion, but does not elaborate on the destructive consequences of folding or betting beyond what the annotation implies.

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 sentences with no wasted words: the primary action and its options are front-loaded, followed by timeout behavior and seed note. Every sentence 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?

Given 9 parameters, 4 required, and no output schema, the description covers the core action and timeout. The schema fully documents all parameters, but the description could mention idempotency_key or shadow for completeness; however, it is adequate for an agent to call correctly.

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 schema already documents all parameters. The description reiterates the amount semantics for bet/raise and mentions the optional seed, but adds no new meaning beyond what the schema provides.

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 states a specific verb (make your move) and resource (poker actions), and enumerates the allowed actions. It does not explicitly differentiate from sibling tools, likely because act is the primary action tool, but that prevents a score of 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?

It provides clear timing context ('when it is your turn') and explains what happens on timeout ('The clock checks or folds for you after to_act.deadline'). No alternatives or exclusions are named, such as referring to the 'seed' sibling for seed-only submissions.

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