Skip to main content
Glama

PokerData

by io.github.hft-studio
OverviewDiscussionsAdmin

Summarize a session

get_session_summary
Read-onlyIdempotent

Headline numbers and HUD rates for one uploaded session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesSession id from list_my_sessions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoSession id.
hudNoHUD rates over this session, as percentages.
heroNoHero name in the history.
errorNoPresent instead of a payload when the request named something that does not exist. No figure is estimated in its place.
handsNoHands in the session.
netBbNoSession result in big blinds.
endedAtNoLast hand timestamp.
game_typeNoGame type: "NLHE", "PLO", "PLO5", or "PLO6".
startedAtNoFirst hand timestamp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / session_id / description
      Added value: +"Session id from list_my_sessions."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Headline numbers and HUD rates for one uploaded session.",
+  "properties": {
+    "endedAt": {
+      "description": "Last hand timestamp.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Present instead of a payload when the request named something that does not exist. No figure is estimated in its place.",
+      "type": "string"
+    },
+    "game_type": {
+      "description": "Game type: \"NLHE\", \"PLO\", \"PLO5\", or \"PLO6\".",
+      "type": "string"
+    },
+    "hands": {
+      "description": "Hands in the session.",
+      "type": "integer"
+    },
+    "hero": {
+      "description": "Hero name in the history.",
+      "type": "string"
+    },
+    "hud": {
+      "description": "HUD rates over this session, as percentages.",
+      "properties": {
+        "limp": {
+          "description": "Open limp, percent.",
+          "type": "number"
+        },
+        "pfr": {
+          "description": "Preflop raise, percent.",
+          "type": "number"
+        },
+        "sample": {
+          "description": "Hands the rates are computed over.",
+          "type": "integer"
+        },
+        "threeBet": {
+          "description": "3-bet, percent.",
+          "type": "number"
+        },
+        "vpip": {
+          "description": "Voluntarily put money in pot, percent.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "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"
+}
  2. First observed

TDQS

B3.2/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 only the scope constraint that it operates on a single already-uploaded session; it discloses nothing about aggregation method or cost.

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?

A single eight-word sentence with no filler and the resource front-loaded. It is efficient, though terse to the point of omitting any actionable usage context.

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, return values need no explanation, and the one parameter is fully described in the schema while annotations carry the safety profile. The definition is adequate for correct invocation, with the main gap being the absence of usage guidance.

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% and the single session_id parameter is fully documented in the schema (UUID format, sourced from list_my_sessions). The description adds no syntax or format meaning beyond that, so the baseline of 3 applies.

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 resource (one uploaded session) and specifies the content returned (headline numbers and HUD rates), which distinguishes it from generic session listings. It does not explicitly contrast with siblings like list_my_sessions or get_board_report, but the scope is unambiguous.

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 when-to-use guidance: no mention of prerequisites (session must be uploaded first), no statement of when this is preferable to get_board_report or other per-session tools, and no exclusions. The only usage hint lives in the schema's session_id description, not the tool description.

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