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

TableJSON 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), "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.
`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

TableJSON 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.

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/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and the closed world, so safety is covered. The description adds real behavioral context: compact mode is paginated, results can be narrowed to avoid huge payloads, and plo9 lacks a spot index entirely — a genuine capability limitation not visible in the schema.

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?

Purpose is front-loaded and every sentence carries information; nothing is redundant with the schema. It is slightly clipped in places (the trailing plo9 sentence lacks a period), but the terse style suits an agent-facing definition.

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 an output schema present, return values need no explanation, and the game enum is fully documented in the schema. The description covers pagination, depth codes, and the plo9 exception, leaving only minor gaps such as default-vs-full detail behavior, which the schema already states.

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 baseline is 3. The description goes beyond it by decoding the depth values (1 = RFI, 2 = vs open, 3 = 3-bet pots), which the schema only labels as an opaque "decision depth filter," and ties contains/offset to the compact pagination workflow.

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 ("Search valid decision nodes") scoped to a stack depth, and differentiates itself from the sibling get_node by contrast. An agent can tell this is the preflop spot index rather than a postflop node or range tool.

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?

Gives concrete usage guidance (use depth, contains, and offset to narrow results without loading thousands of paths) and an explicit when-not case: plo9 has no spot index, so use get_node instead. The alternative and the condition that selects it are both named.

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.

Resources

Need Help?