PokerData

Get an opponent's limp range

get_opponent_limp_range

Read-onlyIdempotent

Shown-hand first-in limp range: 169-class counts of hole cards villains showed after an open limp. Pass position for one seat. Sample is showdown-only. This is not a solver range.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	Yes	Hole-card classes to return, most frequent first, 1 to 169.
`position`	No	Only limps from these seats.
`game_type`	No	Only hands of this game type.
`session_id`	No	Only hands from this upload session.
`table_size`	No	Only hands dealt at tables of this many seats.
`opponent_id`	No	Only this opponent's limps (see list_my_opponents). Omit for every tracked villain.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	That the sample is showdown-only and the counts are observations.
`sample`	No	Shown limped hands behind the counts.
`classes`	No	Observed classes, most frequent first. Counts, not solver frequencies.
`classesByPosition`	No	Seat label to that seat's observed classes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 16, 2026

addedInput schema / properties / game_type / description
```
Added value: +"Only hands of this game type."
```

addedInput schema / properties / limit / description

Added value: +"Hole-card classes to return, most frequent first, 1 to 169."

addedInput schema / properties / opponent_id / description

Added value: +"Only this opponent's limps (see list_my_opponents). Omit for every tracked villain."

addedInput schema / properties / position / description
```
Added value: +"Only limps from these seats."
```
addedInput schema / properties / session_id / description
```
Added value: +"Only hands from this upload session."
```

addedInput schema / properties / table_size / description

Added value: +"Only hands dealt at tables of this many seats."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Shown-hand first-in limp range from uploaded hands. Observed counts, not a solver range.",
+  "properties": {
+    "classes": {
+      "description": "Observed classes, most frequent first. Counts, not solver frequencies.",
+      "items": {
+        "description": "One observed hole-card class.",
+        "properties": {
+          "count": {
+            "description": "Times the class was shown.",
+            "type": "integer"
+          },
+          "hand": {
+            "description": "169-grid class, e.g. AKs.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "classesByPosition": {
+      "additionalProperties": {
+        "description": "Observed classes, most frequent first. Counts, not solver frequencies.",
+        "items": {
+          "description": "One observed hole-card class.",
+          "properties": {
+            "count": {
+              "description": "Times the class was shown.",
+              "type": "integer"
+            },
+            "hand": {
+              "description": "169-grid class, e.g. AKs.",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "description": "Seat label to that seat's observed classes.",
+      "type": "object"
+    },
+    "note": {
+      "description": "That the sample is showdown-only and the counts are observations.",
+      "type": "string"
+    },
+    "sample": {
+      "description": "Shown limped hands behind the counts.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description nonetheless adds substantive caveats beyond them — the sample is showdown-only and shown-hand only, and it is not a solver-derived range. It does not discuss sample-size thresholds or filtering behavior, but the added context is meaningful.

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?

Three tight clauses, front-loaded with what the tool returns, then the invocation hint, then the two caveats. Telegraphic but every clause carries information; no filler.

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 the description need not explain return values, and it supplies the key interpretive caveats (showdown-only, not a solver range). For a 6-parameter filterable analytics tool whose schema is fully documented, this is close to complete, though a note on sparsity/sample confidence would help.

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%, so every one of the 6 parameters is already documented in the schema. The description only adds 'Pass position for one seat', which sits slightly awkwardly against the schema's array-of-seats semantics and provides marginal extra meaning. Baseline 3 is appropriate.

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 precise verb+resource (observed limp range) plus the exact output form (169-class hole-card counts) and the population (hole cards villains showed after an open limp). The closing 'This is not a solver range' explicitly separates it from solver-range siblings such as get_range and get_postflop_range.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the solver-range disclaimer and 'Sample is showdown-only' hint at when the data is appropriate, and 'Pass position for one seat' is a light invocation hint. However, no explicit when-to-use/when-not conditions or named alternative tools are given beyond the negation.

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?