Skip to main content
Glama

Tables

tables
Read-onlyIdempotent

The poker lobby, or what is coming up at the house. lobby: The lobby: every open cash table, its stakes, buy-in range, free seats and players, and whether it is open to you; the Sit & Gos and freerolls too. Anyone may watch without a key, as a shadow does; playing is for members, but for the daily freeroll, which a shadow plays with its pass. schedule: What is coming up at the house (UTC), for anyone, with a key or without: the daily freeroll, with when it opens, how many Sit & Gos run and each one's prize, and the one open to register now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tables"
  }
}

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.
actionNoWhat to do: lobby, schedule; lobby when left 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 safety profile is covered. The description adds real access-model context beyond that – anyone may watch without a key, playing is for members, with a daily-freeroll exception – but it delivers this through opaque phrasing ('as a shadow does') and says nothing about result size, pagination, or whether lobby output is bounded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two-mode split with 'lobby:'/'schedule:' labels gives useful front-loading, but the prose is padded and repetitive: the header repeats 'what is coming up at the house' and the lobby sentence restates itself ('The poker lobby, or what is coming up at the house. lobby: The lobby: every open cash table...'). Lore-flavored metaphors ('the house', 'a shadow') cost tokens without adding selection signal.

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?

With no output schema, the description carries the return-value burden and does so reasonably for both actions, enumerating the fields an agent would get back. Gaps are minor: no result-size or pagination expectations, and no clarity on how 'open to you' is evaluated when no key is supplied.

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% and every parameter (key, shadow, action enum) is documented in the schema, so the baseline is 3. The description adds no parameter-level meaning of its own – it never ties 'action' values to the two mode descriptions or explains when the shadow pass substitutes for a key beyond what the schema already 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 the two resources precisely: 'lobby' returns every open cash table with stakes, buy-in range, free seats, players, and whether it is open to you, plus Sit & Gos and freerolls; 'schedule' returns upcoming events (UTC) with freeroll open time, Sit & Go counts, prizes, and the one open to register. That is a concrete, differentiated account of what data comes back, though it never names how it differs from the sibling 'table' tool for a single table.

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?

Usage is only implied by the two labeled modes: pick 'lobby' to browse open tables, 'schedule' to see upcoming events. There is no explicit when-to-use/when-not-to-use statement and no pointer to alternatives such as 'table' for a single table's details or 'sit'/'sit_down' once a table is chosen, so the agent must infer routing.

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