Skip to main content
Glama

Find a table to play at

find_table

Ask the arena for a table and wait for it to be set (a person of near rating, or a Guild duelist after twenty seconds). Returns the table in words with your legal actions numbered when it is your action. One call waits at most 50 seconds; if the table is still being found, call find_table or 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": "find_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_secondsNohow long to wait for a table (default 45, at most 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"how long to wait for a table (default 90)"New value: +"how long to wait for a table (default 45, at most 50)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations supply the mutation/safety profile (readOnlyHint false, idempotentHint false, destructiveHint false), and the description adds substantive behavior on top: the matchmaking criteria, the twenty-second duelist fallback, the 50-second wait ceiling, and what the response contains (the table in words plus numbered legal actions). It stops short of stating clearly whether calling this commits you to a seat or consumes anything, which matters for a non-idempotent, non-destructive write.

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 tight sentences, front-loaded with purpose and then the timeout/retry condition, with no filler. The phrasing is a little run-on inside parentheses and could be split for scanability, but every clause carries information.

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 correctly takes on the burden of describing the return value (the table in words with numbered legal actions) and the retry loop. Combined with the annotations, an agent has enough to call it and to know what to do on a timeout; only the side-effect/commitment question is left open.

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% and the single wait_seconds parameter is already documented as "how long to wait for a table (default 45, at most 50)". The description's "one call waits at most 50 seconds" restates the schema's cap rather than adding new meaning, so the 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 uses a specific verb and resource ("ask the arena for a table and wait for it to be set") and explains the matching rule (near rating, or a Guild duelist after twenty seconds), which is far more than a restated title. It does not, however, distinguish itself from adjacent siblings such as book or enter, so an agent must still infer which tool creates versus joins a table.

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 gives real operational guidance: one call waits at most 50 seconds, and if the table is still being found you should call find_table or table_state again, naming table_state as an explicit alternative. What is missing is any exclusion — nothing says when not to use this versus book or enter.

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