PokerData

Get my results curve

get_hand_results

Read-onlyIdempotent

Per-hand cumulative results for a winnings curve. points is [{ hand, bb }], oldest to newest, downsampled. Pass session_id for one session. 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
`max_points`	Yes	Points on the curve after downsampling, 2 to 200.
`session_id`	No	Only this upload session's hands. Omit for the whole account.

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No	Where to upload hands when the account has none.
`netBb`	No	Final cumulative result in big blinds.
`points`	No	Downsampled curve, oldest to newest.
`totalHands`	No	Hands behind the curve.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 16, 2026

addedInput schema / properties / max_points / description

Added value: +"Points on the curve after downsampling, 2 to 200."

addedInput schema / properties / session_id / description

Added value: +"Only this upload session's hands. Omit for the whole account."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Cumulative result per hand, for a winnings curve.",
+  "properties": {
+    "hint": {
+      "description": "Where to upload hands when the account has none.",
+      "type": "string"
+    },
+    "netBb": {
+      "description": "Final cumulative result in big blinds.",
+      "type": "number"
+    },
+    "points": {
+      "description": "Downsampled curve, oldest to newest.",
+      "items": {
+        "description": "One point on the curve.",
+        "properties": {
+          "bb": {
+            "description": "Cumulative result in big blinds.",
+            "type": "number"
+          },
+          "hand": {
+            "description": "Hand number, oldest first.",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalHands": {
+      "description": "Hands behind the curve.",
+      "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 declare the safe read-only/idempotent profile, so the bar is lower. The description still adds real value beyond them: the curve is downsampled, ordered oldest to newest, and formats points as [{ hand, bb }], plus empty-state guidance to route to the upload page.

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?

Front-loads the purpose, then output shape, then the one parameter, then the empty-state fallback. Dense but every sentence carries information; slightly compressed with the inline backtick notation.

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 doesn't need to explain returns, yet it usefully summarizes the curve format. Empty-account behavior is covered, so an agent has enough to call and recover from the zero-hands case.

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 coverage is 100%, so both parameters are already documented. The description restates session_id scoping ('Pass session_id for one session') but adds no syntax or behavior beyond the schema; the points format described is output, not a parameter. Baseline 3 is appropriate.

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 names a specific verb+resource: a per-hand cumulative results curve of winnings. It is distinguishable from siblings like get_session_summary or get_tournament_results by the per-hand granularity, though it doesn't explicitly contrast itself with those tools.

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 gives clear context: pass session_id to scope to one session, and instructs the agent to fall back to the upload page from get_upload_link when the account has no hands. It stops short of explicitly naming alternative tools for aggregated stats.

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?