PokerData

List my opponents

list_my_opponents

Read-onlyIdempotent

Tracked opponents from uploaded hands. Each row has handCount, handsVsHero, and heroBb100Vs. Pass name to find one villain.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hero`	No	Only hands where this hero name was seated.
`name`	No	Case-insensitive substring of the opponent's screen name.
`sort`	Yes	Row order: most hands, most recent, or by hero's bb/100 against them (toughest = worst for hero).	hands
`limit`	Yes	Opponents to return, 1 to 500.
`game_type`	No	Only hands of this game type, e.g. "NLHE" or "PLO".
`min_hands`	Yes	Drop opponents seen in fewer hands than this.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`opponents`	No	Opponents, sorted as requested.

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, e.g. \"NLHE\" or \"PLO\"."

addedInput schema / properties / hero / description

Added value: +"Only hands where this hero name was seated."

addedInput schema / properties / limit / description
```
Added value: +"Opponents to return, 1 to 500."
```

addedInput schema / properties / min_hands / description

Added value: +"Drop opponents seen in fewer hands than this."

addedInput schema / properties / name / description

Added value: +"Case-insensitive substring of the opponent's screen name."

addedInput schema / properties / sort / description

Added value: +"Row order: most hands, most recent, or by hero's bb/100 against them (toughest = worst for hero)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Opponents tracked across this account's uploaded hands.",
+  "properties": {
+    "opponents": {
+      "description": "Opponents, sorted as requested.",
+      "items": {
+        "description": "One opponent.",
+        "properties": {
+          "cbetFaced": {
+            "description": "Flop c-bets the opponent faced.",
+            "type": "integer"
+          },
+          "cbetFold": {
+            "description": "Those c-bets the opponent folded to.",
+            "type": "integer"
+          },
+          "displayName": {
+            "description": "Screen name as written in the history.",
+            "type": "string"
+          },
+          "gameTypes": {
+            "description": "Game types seen.",
+            "items": {
+              "description": "Game type.",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "handCount": {
+            "description": "Hands the opponent appears in.",
+            "type": "integer"
+          },
+          "handsVsHero": {
+            "description": "Hands played against hero.",
+            "type": "integer"
+          },
+          "heroBb100Vs": {
+            "description": "Hero's bb/100 in hands against this opponent.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "heroes": {
+            "description": "Hero accounts that faced this opponent.",
+            "items": {
+              "description": "Hero name.",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Opponent id for get_opponent_notes.",
+            "type": "string"
+          },
+          "lastSeen": {
+            "description": "Most recent hand timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "net": {
+            "description": "Hero's net big blinds in those hands.",
+            "type": "number"
+          },
+          "notes": {
+            "description": "Leak notes.",
+            "items": {
+              "description": "One leak note with its sample size.",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "notesCount": {
+            "description": "Leak notes available.",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the shape of each returned row (handCount, handsVsHero, heroBb100Vs), which is useful behavioral context, but says nothing about defaults, caps, or empty-result behavior.

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 short sentences, front-loaded with the data source before the row shape and the filter hint; nothing is wasted. Slight deduction because the row field names are dropped without context, leaving the reader to interpret heroBb100Vs on their own.

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 returns, and the schema fully covers all six parameters plus required/minimum constraints. For a read-only list tool this is close to complete; the missing piece is any hint about the typical workflow connecting this to the per-opponent siblings.

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% and every parameter is documented in-schema, including the sort enum semantics and the 1-500 limit range, so the baseline is 3. The description only echoes the name filter ('find one villain') and does not add meaning beyond the schema, e.g. how it interacts with hero or min_hands.

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?

States a specific resource and scope: tracked opponents derived from uploaded hands, which an agent can distinguish from session/hand-level siblings. It does not explicitly name a sibling, so it stops short of a 5, but the verb+resource pairing is clear.

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?

The only guidance is 'Pass name to find one villain,' which implies a lookup use case but gives no when-to-use versus when-not-to-use, and no routing to alternatives like get_opponent_notes for notes on a specific villain. Usage is implied rather than stated.

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?