PokerData

Search preflop spots

list_spots

Read-onlyIdempotent

Search valid decision nodes for a stack depth, tagged by depth (1 = RFI, 2 = vs open, 3 = 3-bet pots, …). Compact mode is paginated; use depth, contains, and offset to narrow results without loading thousands of paths. plo9 has no spot index: walk it with get_node from history "UTG".

Input Schema

Name	Required	Description
`game`	Yes	"nl" = no-limit hold'em 6-max cash (169-grid hands, per-hand EV in small blinds), "nl9" = no-limit hold'em 9-max cash, "nlmtt8" = no-limit hold'em 8-max MTT chip-EV (10–300bb, 1bb BB-ante; Fold/Call/Limp/AI/Open/3B tokens), "nlh8-hydra" = no-limit hold'em 8-max MTT chip-EV with a classic 0.1bb ante from every seat (10, 20, 30, 60bb; same tokens as nlmtt8), "nlh8-icm" = no-limit hold'em 8-max MTT with ICM: one stack table per scenario (near the money, 33 or 35 left of 200, 30 paid; final table, 8 left), uneven stacks, 0.125bb ante from every seat, EVs in tournament dollars; pass scenario (list_games lists them; stack alone works only where one table has that depth); get_node only, "nlhu" = no-limit hold'em heads-up for the title, chip-EV, both players at the stack (1–40bb), 0.125bb ante each, SB on the button; get_node only, "plo" = pot-limit Omaha 6-max cash (4-card), "plo5" = pot-limit Omaha 5-card 6-max (100bb, 1.2bb ante), "plo9" = pot-limit Omaha 9-max cash, "plo6hu" = 6-card Omaha heads-up (BTN vs BB, 100bb). Cash trees are not tournament, ICM, PKO, or satellite solves. nlmtt8, nlh8-hydra and nlhu are chip-EV; only nlh8-icm is ICM.
`depth`	No	Optional decision depth filter
`limit`	No	Maximum compact rows to return (default 120, maximum 500).
`stack`	Yes	Stack depth in big blinds
`detail`	No	Response detail. "compact" is the default and removes bulk maps; use "full" only when exact complete data is required.
`offset`	No	Compact pagination offset
`contains`	No	Optional case-insensitive history substring filter

Output Schema

Name	Required	Description
`game`	No	Game id.
`hint`	No	How to narrow, page, or widen the same query.
`spots`	No	This page of decision nodes.
`stack`	No	Stack depth in big blinds.
`total`	No	Spots in the dataset for this stack.
`offset`	No	Offset this page started at.
`matched`	No	Spots left after the depth and contains filters.
`returned`	No	Spots in this page.
`nextOffset`	No	Offset for the next page, or null at the end.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

changedInput schema / properties / game / description

Previous value: -"\"nl\" = no-limit hold'em 6-max cash (169-grid hands, per-hand EV in small blinds), \"nl9\" = no-limit hold'em 9-max cash, \"nlmtt8\" = no-limit hold'em 8-max MTT chip-EV (10–300bb, 1bb BB-ante; Fold/Call/Limp/AI/Open/3B tokens), \"nlh8-hydra\" = no-limit hold'em 8-max MTT chip-EV with a classic 0.1bb ante from every seat (10, 20, 30, 60bb; same tokens as nlmtt8), \"plo\" = pot-limit Omaha 6-max cash (4-card), \"plo5\" = pot-limit Omaha 5-card 6-max (100bb, 1.2bb ante), \"plo9\" = pot-limit Omaha 9-max cash, \"plo6hu\" = 6-card Omaha heads-up (BTN vs BB, 100bb). Cash trees are not tournament, ICM, PKO, or satellite solves. nlmtt8 is chip-EV only."New value: +"\"nl\" = no-limit hold'em 6-max cash (169-grid hands, per-hand EV in small blinds), \"nl9\" = no-limit hold'em 9-max cash, \"nlmtt8\" = no-limit hold'em 8-max MTT chip-EV (10–300bb, 1bb BB-ante; Fold/Call/Limp/AI/Open/3B tokens), \"nlh8-hydra\" = no-limit hold'em 8-max MTT chip-EV with a classic 0.1bb ante from every seat (10, 20, 30, 60bb; same tokens as nlmtt8), \"nlh8-icm\" = no-limit hold'em 8-max MTT with ICM: one stack table per scenario (near the money, 33 or 35 left of 200, 30 paid; final table, 8 left), uneven stacks, 0.125bb ante from every seat, EVs in tournament dollars; pass scenario (list_games lists them; stack alone works only where one table has that depth); get_node only, \"nlhu\" = no-limit hold'em heads-up for the title, chip-EV, both players at the stack (1–40bb), 0.125bb ante each, SB on the button; get_node only, \"plo\" = pot-limit Omaha 6-max cash (4-card), \"plo5\" = pot-limit Omaha 5-card 6-max (100bb, 1.2bb ante), \"plo9\" = pot-limit Omaha 9-max cash, \"plo6hu\" = 6-card Omaha heads-up (BTN vs BB, 100bb). Cash trees are not tournament, ICM, PKO, or satellite solves. nlmtt8, nlh8-hydra and nlhu are chip-EV; only nlh8-icm is ICM."

changedInput schema / properties / game / enum

Previous value: -[
-  "nl",
-  "nl9",
-  "nlmtt8",
-  "nlh8-hydra",
-  "plo",
-  "plo5",
-  "plo9",
-  "plo6hu"
-]New value: +[
+  "nl",
+  "nl9",
+  "nlmtt8",
+  "nlh8-hydra",
+  "nlh8-icm",
+  "nlhu",
+  "plo",
+  "plo5",
+  "plo9",
+  "plo6hu"
+]

Changed1 schema field changedOct 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Valid decision nodes for one game and stack, paginated.",
+  "properties": {
+    "game": {
+      "description": "Game id.",
+      "type": "string"
+    },
+    "hint": {
+      "description": "How to narrow, page, or widen the same query.",
+      "type": "string"
+    },
+    "matched": {
+      "description": "Spots left after the depth and contains filters.",
+      "type": "integer"
+    },
+    "nextOffset": {
+      "description": "Offset for the next page, or null at the end.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "offset": {
+      "description": "Offset this page started at.",
+      "type": "integer"
+    },
+    "returned": {
+      "description": "Spots in this page.",
+      "type": "integer"
+    },
+    "spots": {
+      "description": "This page of decision nodes.",
+      "items": {
+        "description": "One decision node.",
+        "properties": {
+          "actor": {
+            "description": "Position to act.",
+            "type": "string"
+          },
+          "depth": {
+            "description": "Decision depth: 1 = RFI, 2 = vs open, 3 = 3-bet pots.",
+            "type": "integer"
+          },
+          "history": {
+            "description": "Action path ending in the acting position.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "stack": {
+      "description": "Stack depth in big blinds.",
+      "type": "number"
+    },
+    "total": {
+      "description": "Spots in the dataset for this stack.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavior beyond that: compact mode is paginated, large result sets should be narrowed, and plo9 has no spot index. It does not discuss return shape, but an output schema exists.

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?

The description is short and front-loads the core action before pagination advice and the plo9 exception. Every sentence carries useful information, though the plo9 instruction is somewhat abrupt and could be clearer in context.

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?

Given rich annotations, complete schema coverage, and an output schema, the description provides enough context to call the tool correctly. It covers pagination, depth tagging, narrowing filters, and the important plo9 exception. Remaining gaps are minor because structured fields already carry much of the detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema does most parameter documentation. The description still adds value by explaining the depth tag meanings (1 = RFI, 2 = vs open, 3 = 3-bet pots) and by recommending depth, contains, and offset for narrowing results. It does not add much for game, stack, limit, or detail beyond the schema.

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 verb and resource: searching valid preflop decision nodes by stack depth, with depth tags. It also names the get_node alternative for plo9, giving useful sibling differentiation, though the core phrase 'spots' is only implicitly the decision-node index.

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 clearly explains the main usage pattern: use depth, contains, and offset to narrow results and avoid loading thousands of paths. It also gives an explicit when-not case for plo9 by directing users to get_node. It does not broadly compare against all sibling search/get tools, but the practical guidance is clear.

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

All PokerData 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.