PokerData

Upload a hand history

upload_hand_history

Secondary upload path for a small paste. Prefer get_upload_link and the hosted /upload page. Runs the same ingestion pipeline and returns hands parsed, tournaments parsed, and errors. Does not grade solver frequencies.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Raw hand history or tournament summary text.
`filename`	No	Name to record for the paste. Defaults to "paste.txt".

Output Schema

TableJSON Schema

Name	Required	Description
`errors`	No	Parse errors, if any.
`filename`	No	Filename recorded for the paste.
`persisted`	No	Always false: nothing is written to durable storage.
`sessionId`	No	Session id for the stored hands, or null when nothing parsed.
`handsParsed`	No	Hands parsed.
`persistence`	No	Where the hands live, "process_memory".
`tournamentsParsed`	No	Tournament summaries parsed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

addedInput schema / properties / filename / description

Added value: +"Name to record for the paste. Defaults to \"paste.txt\"."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Result of ingesting one pasted hand history.",
+  "properties": {
+    "errors": {
+      "description": "Parse errors, if any.",
+      "items": {
+        "description": "One parse error.",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "filename": {
+      "description": "Filename recorded for the paste.",
+      "type": "string"
+    },
+    "handsParsed": {
+      "description": "Hands parsed.",
+      "type": "integer"
+    },
+    "persisted": {
+      "description": "Always false: nothing is written to durable storage.",
+      "type": "boolean"
+    },
+    "persistence": {
+      "description": "Where the hands live, \"process_memory\".",
+      "type": "string"
+    },
+    "sessionId": {
+      "description": "Session id for the stored hands, or null when nothing parsed.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tournamentsParsed": {
+      "description": "Tournament summaries parsed.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description adds real context beyond them: it shares the same ingestion pipeline as the hosted path and reports hands parsed, tournaments parsed, and errors. It omits that repeated uploads are non-idempotent, which is the one meaningful behavioral gap.

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 with no filler, and the identity plus the routing advice are front-loaded. The trailing scope exclusion earns its place, though the returns sentence partly duplicates the output schema.

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 explained, and the description still covers purpose, routing, and scope limits. The remaining gap is the non-idempotent nature of re-uploading the same paste, which the description never warns about.

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 (text, filename) are already fully documented. The description only implies a size expectation via 'small paste' and adds no format or content detail beyond the schema, so the baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (upload a hand history paste) and immediately positions itself as a secondary path versus the primary sibling get_upload_link. An agent can tell it apart from the other upload route without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names the preferred alternative (get_upload_link and the hosted /upload page) and the condition that selects this tool instead (a small paste). It also states a scope exclusion — it does not grade solver frequencies — leaving nothing 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 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?