Skip to main content
Glama

PokerData

by io.github.hft-studio
OverviewDiscussionsAdmin

List solved datasets

list_datasets
Read-onlyIdempotent

List preflop datasets in the shipped tree documentation (stacks, positions, whether each bundle was analyzed). Preflop exploitability is not available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
readmeNoHow to read one dataset's write-up.
sourceNoWhere the documentation came from, "data/tree-docs".
datasetsNoDocumented datasets.
generatedNoDate the documentation was generated.
preflopExploitabilityNoAlways "not available": no preflop dataset publishes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Preflop datasets in the shipped tree documentation.",
+  "properties": {
+    "datasets": {
+      "description": "Documented datasets.",
+      "items": {
+        "description": "One dataset.",
+        "properties": {
+          "analyzed": {
+            "description": "Rows whose bundle was analyzed.",
+            "type": "integer"
+          },
+          "formats": {
+            "description": "Formats in the index.",
+            "items": {
+              "description": "Format label.",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Dataset id to pass to get_tree_docs, e.g. \"nl/v2\".",
+            "type": "string"
+          },
+          "perNode": {
+            "description": "True when index rows are per node rather than per bundle.",
+            "type": "boolean"
+          },
+          "positions": {
+            "description": "Positions with index rows.",
+            "items": {
+              "description": "Seat label.",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "rows": {
+            "description": "Index rows for the dataset.",
+            "type": "integer"
+          },
+          "stacks": {
+            "description": "Covered stack depths.",
+            "items": {
+              "description": "Stack depth in big blinds.",
+              "type": "number"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "generated": {
+      "description": "Date the documentation was generated.",
+      "type": "string"
+    },
+    "preflopExploitability": {
+      "description": "Always \"not available\": no preflop dataset publishes it.",
+      "type": "string"
+    },
+    "readme": {
+      "description": "How to read one dataset's write-up.",
+      "type": "string"
+    },
+    "source": {
+      "description": "Where the documentation came from, \"data/tree-docs\".",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, read-only, idempotent, closed-world read, so the safety profile is covered. The description adds value beyond them by describing the content each entry carries and by flagging the key limitation (no preflop exploitability), which prevents the agent from misusing the results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with the resource and scope front-loaded and the limitation trailing. Every clause carries information (what is listed, where it lives, what fields appear, what is unavailable) with 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?

An output schema exists so return values need not be spelled out, and annotations cover the safety profile; the description supplies the remaining needed context (scope, per-entry content, one absence). Only the differentiation from sibling listing tools is left implicit.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. No parameter semantics are missing or contradicted.

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 verb (List) and resource (preflop datasets) and adds scope: they live in the shipped tree documentation, and it enumerates what each entry conveys (stacks, positions, analyzed status). It does not name or distinguish itself from similar siblings such as list_postflop_packs or get_tree_docs, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no alternatives named among a large family of list_* siblings. The closing caveat 'Preflop exploitability is not available' hints at what the tool cannot do, but it is not framed as routing guidance, leaving usage to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PokerData toolsInspect
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