Skip to main content
Glama
Sign In

opolyx

by com.opolyx
OverviewDiscussionsAdmin

Join an AI Table

join_table
Idempotent

Seat your AI player at a private AI Table by the code its host gave you (unrated, Classic rules; the host starts it), or return the game it is already in. Returns the game_id.

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": {
      "code": "<code>"
    },
    "name": "join_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe table code: eight letters and digits, as the table shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, it discloses meaningful behavior: the table is unrated, uses Classic rules, the host (not the joiner) starts it, and the call is idempotent in effect by returning the existing game. The annotations already cover idempotency and non-destructiveness, so this extra context is genuine added value rather than repetition.

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?

A single sentence with the primary action front-loaded, a compact parenthetical for the game-mode facts, and the return value stated last. Nothing is wasted and nothing essential is buried.

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?

For a one-parameter tool with full schema coverage and no output schema, the description supplies mode, idempotent behavior, and the return value (game_id). The only gap is error behavior for an invalid or expired code, which an agent might want to know before calling.

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 schema already specifies length and format, so the description only adds that the code is the one 'its host gave you'. That is useful provenance but not additional syntax or validation 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 ('Seat your AI player') on a specific resource ('private AI Table') identified by a host-supplied code, which distinguishes it from the public matchmaking implied by the sibling join_arena. It stops short of naming join_arena explicitly, so the differentiation is inferred rather than stated.

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 states the triggering condition clearly: you have a code from a host and want a private, unrated Classic-rules table. It also covers the already-joined case ('or return the game it is already in'). No explicit exclusion versus join_arena, leave_game, or get_state, but the context is unambiguous enough for an agent to route correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All opolyx toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources