PokerData

Get my tournament results

get_tournament_results

Read-onlyIdempotent

MTT results imported from tournament summary files. Money is in cents. Hand histories are not a source of buy-ins or prizes. 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	Tournament summaries to include, 1 to 500.

Output Schema

TableJSON Schema

Name	Required	Description
`roi`	No	Return on investment as a ratio, or null.
`note`	No	Present when no tournament summaries have been uploaded.
`itmPct`	No	Share of tournaments that cashed, 0 to 1, or null.
`recent`	No	Tournaments, newest first.
`buyInCents`	No	Total buy-ins, or null when one buy-in is unknown.
`tournaments`	No	Tournament summaries counted.
`receivedCents`	No	Total prize money received.
`netProfitCents`	No	Received minus buy-ins, or null when a buy-in is unknown.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

addedInput schema / properties / limit / description

Added value: +"Tournament summaries to include, 1 to 500."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "MTT results from uploaded tournament summaries. Money is in cents.",
+  "properties": {
+    "buyInCents": {
+      "description": "Total buy-ins, or null when one buy-in is unknown.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "itmPct": {
+      "description": "Share of tournaments that cashed, 0 to 1, or null.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "netProfitCents": {
+      "description": "Received minus buy-ins, or null when a buy-in is unknown.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "note": {
+      "description": "Present when no tournament summaries have been uploaded.",
+      "type": "string"
+    },
+    "receivedCents": {
+      "description": "Total prize money received.",
+      "type": "number"
+    },
+    "recent": {
+      "description": "Tournaments, newest first.",
+      "items": {
+        "description": "One tournament.",
+        "properties": {
+          "buyInCents": {
+            "description": "Buy-in in cents.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "fieldSize": {
+            "description": "Entrants.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "finish": {
+            "description": "Finishing place.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "game": {
+            "description": "Game label from the summary.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Row id.",
+            "type": "string"
+          },
+          "receivedCents": {
+            "description": "Prize received in cents.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "sourceId": {
+            "description": "Tournament id from the summary file.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "roi": {
+      "description": "Return on investment as a ratio, or null.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "tournaments": {
+      "description": "Tournament summaries counted.",
+      "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, closed-world), so the description correctly spends its words on added context: money is denominated in cents and hand histories are not a source of buy-ins or prizes. This is meaningful data-shape information beyond the annotations.

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?

Four short sentences, front-loaded with what the data is, then units and caveats, then the fallback workflow. No filler, though the upload-link sentence is long enough that it could be tightened.

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 return-value explanation is unnecessary, and the description covers provenance, currency units, and a fallback path. It does not state what happens when there are zero tournaments (as opposed to zero hands), a minor gap for a single-parameter read tool.

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% for the single `limit` parameter (1–500, default 200), so the schema fully documents it. The description adds nothing about the limit or result windowing, which is the expected baseline-3 outcome when the schema does the heavy lifting.

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 identifies the resource and its provenance ("MTT results imported from tournament summary files"), which tells an agent this returns tournament-level results rather than hand results. It is clear but does not explicitly contrast with siblings like get_hand_results or get_session_summary.

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 a concrete conditional workflow: when the account has no hands, offer the hosted upload page from get_upload_link instead of asking for pasted histories. That is real usage guidance, though there is no explicit when-to-use framing versus other results tools.

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?