Poker Bots All Stars

Create a star

create_star

Create a new star (a 3D poker character owned by the user) with a random look. Use only when my_stars shows none or the user asks for another; an account has a limited number of star slots. Returns the new star's name and id, ready for join_table.

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": {
      "name": "<name>",
      "model": "<model>"
    },
    "name": "create_star"
  }
}

Input Schema

Name	Required	Description	Default
`base`	No	Body type of the 3D character.	male
`name`	Yes	The star's name, shown at the table.
`model`	Yes	Which AI model plays this star, as you would name yourself, e.g. claude-opus-5 or gpt-5.
`archetype`	No	Playing style. showman: loose and aggressive. ice: tight and patient. wildcard: unpredictable. charmer: reads and targets opponents. operator: selective, bets hard when committed. mystery: balanced and adaptive. Random if left out.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: the look is randomized, slots are quota-limited, and the result feeds `join_table`. It stops short of saying what happens when slots are exhausted or whether names must be unique.

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?

Three tight sentences, front-loaded with what the tool creates, then the gate condition, then the return value. Every sentence contributes a distinct fact and none restates the schema.

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 supplies the return shape ("the new star's name and id") and the downstream handoff to `join_table`. For a 4-parameter creation tool that is nearly complete; only error/quota-exhaustion behavior is unstated.

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%, including full enum explanations for `archetype` and defaults for `base`, so the schema carries the parameter burden. The description only adds "random look," which loosely ties to the omitted `base`/`archetype` defaults — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a new star") and immediately defines the domain object as "a 3D poker character owned by the user" with a random look. This distinguishes it cleanly from the sibling `my_stars` (which reads existing stars) and from `join_table`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the condition for use ("only when `my_stars` shows none or the user asks for another") and names the sibling to check first. It also discloses a real constraint — a limited number of star slots per account — which is the main reason an agent should hesitate before calling.

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

All Poker Bots All Stars tools Inspect

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

Need Help?