Skip to main content
Glama

Read the table as it stands

table_state
Read-onlyIdempotent

The table as it stands, in words: the clock, the pool, both chains, your hand, the market, the columns, the last events, and every legal action as a numbered line. Waits up to wait_seconds (at most 50) for your action when it is theirs; if it is still theirs, call table_state again.

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": "table_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_secondsNowait for your action this long (default 40, at most 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"wait for your action this long (default 40)"New value: +"wait for your action this long (default 40, at most 50)"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world behavior, but the description adds something not in them: this call blocks up to wait_seconds (max 50) waiting for the agent's turn, and may need to be re-invoked. That blocking/turn-taking trait is material for an agent deciding how to poll, and the enumerated return contents add useful shape information.

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?

It is short and front-loaded, but the list of return contents uses opaque in-game jargon ('the pool', 'both chains', 'your hand') that a fresh agent may not resolve, and the 50-second cap is stated twice. Every clause is arguably load-bearing, yet the phrasing costs clarity.

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 state components plus numbered legal actions. Combined with the blocking-wait explanation, an agent has enough to call it correctly; only the meaning of the domain terms is under-specified.

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 the single parameter already documents 'wait for your action this long (default 40, at most 50)'. The description only restates the cap ('at most 50') without adding syntax, units nuance, or what happens at the boundary, so 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 states a specific resource read ('the table as it stands') and enumerates exactly what is returned: clock, pool, both chains, hand, market, columns, last events, and numbered legal actions. That is far more specific than the title alone, though it never names a sibling tool (e.g. act, brief, result) to contrast with, so sibling differentiation is left to the agent.

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 one concrete usage rule: wait up to wait_seconds for your action when it is theirs, and call table_state again if it is still theirs. That is useful retry-loop guidance, but there is no statement of when to prefer this over alternatives such as act or brief, so guidance is implied rather than explicit.

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