PokerData

List my sessions

list_my_sessions

Read-onlyIdempotent

Recent uploaded sessions, newest first: id, hero, game type, dates, hands, and net result. game_type matches hole-card count. If this account has no hands, offer the hosted upload page from get_upload_link (https://pokerdata.io/upload) instead of asking the user to paste histories into chat.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	Yes	Sessions to return, 1 to 50.
`game_type`	No	Only sessions containing this game type.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No	Where to upload hands when the account has none.
`sessions`	No	Sessions, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 16, 2026

addedInput schema / properties / game_type / description

Added value: +"Only sessions containing this game type."

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Recent uploaded sessions, newest first.",
+  "properties": {
+    "hint": {
+      "description": "Where to upload hands when the account has none.",
+      "type": "string"
+    },
+    "sessions": {
+      "description": "Sessions, newest first.",
+      "items": {
+        "description": "One upload session.",
+        "properties": {
+          "endedAt": {
+            "description": "Last hand timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "filename": {
+            "description": "Uploaded filename.",
+            "type": "string"
+          },
+          "game_type": {
+            "description": "Dominant game type in the session.",
+            "type": "string"
+          },
+          "game_types": {
+            "description": "Every game type in the session.",
+            "items": {
+              "description": "Game type.",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "hands": {
+            "description": "Hands in the session.",
+            "type": "integer"
+          },
+          "hero": {
+            "description": "Hero name in the history.",
+            "type": "string"
+          },
+          "id": {
+            "description": "Session id.",
+            "type": "string"
+          },
+          "netBb": {
+            "description": "Session result in big blinds.",
+            "type": "number"
+          },
+          "startedAt": {
+            "description": "First hand timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "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?

Annotations already establish read-only, idempotent, non-destructive behavior, so the description is free to add other context — and it does: newest-first ordering and the empty-state fallback flow. It does not mention pagination or result-size behavior, a minor gap for a listing tool.

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?

Two sentences, front-loaded with the core purpose and return fields, then the fallback instruction. Efficient and free of filler, though the second sentence packs two distinct ideas into one line.

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?

An output schema exists, so field-level return explanation is optional, yet the description still names key fields and the sort order. Combined with the empty-account fallback, an agent has enough to call this correctly, with only pagination behavior unaddressed.

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, but the description adds real meaning beyond the schema by explaining that 'game_type matches hole-card count', which clarifies the NLHE/PLO/PLO5/PLO6 enum semantics. The limit parameter is left entirely to 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?

Specific verb+resource ('Recent uploaded sessions') with a clear scope signal ('newest first') and an enumeration of returned fields, which separates it from detail-oriented siblings like get_session_summary. It stops short of explicitly naming the sibling it differs from, so it is clear but not fully self-differentiating.

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?

Gives explicit conditional routing for the empty-account case: fall back to get_upload_link rather than asking the user to paste histories. That is a concrete when-to-use rule, but there is no guidance on when to prefer this list view over get_session_summary or find_hands for detail.

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?