Skip to main content
Glama

Table

table
Read-onlyIdempotent

See a table: the seats, stacks and bets, the board and pots, whose turn it is and until when, your own cards (never anyone else's), and the commitment to the next hand. Anyone may watch without a key, as a shadow does, and sees no cards but the board's; a shadow playing the daily freeroll sends its pass and sees its own.

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

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.
tableYesThe table's id, as the lobby (tables) lists it.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower, but the description still adds substantive access-control behavior: you see your own cards and 'never anyone else's', and keyless watchers see only the board. That visibility asymmetry is not derivable from the annotations or schema and is the most valuable sentence here.

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?

Two sentences, no filler, with the purpose and returned fields front-loaded. The second sentence is heavily compressed and grammatically tangled ('as a shadow does, and sees no cards but the board's'), which slightly taxes comprehension but not length.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so by enumerating the table state fields. Auth and spectator modes are covered; missing are edge behaviors such as a nonexistent or expired table, but for a read tool this is close to complete.

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 coverage is 100%, with each of the three parameters already documented in detail, so the baseline applies. The description loosely echoes the `shadow` parameter ('sends its pass') but adds no format, constraint, or interaction detail beyond what the schema states.

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 read operation and enumerates exactly what state is returned: seats, stacks and bets, board and pots, turn and clock, own cards, and next-hand commitment. That inventory makes the tool distinguishable from write siblings like `sit_down` or `act`, though it never explicitly contrasts itself with `tables` (the lobby) or `hand`, leaving the reader to infer the boundary.

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 gives real context on the two authentication paths: unauthenticated callers may watch as a shadow and see only the board, while a shadow holding a daily freeroll pass should send it. What's missing is when to prefer this over `tables`, `hand`, or `board`, and any explicit exclusions or failure conditions.

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