PokerData

Upload a hand history

upload_hand_history

Destructive

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

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

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.1/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false), so the description's job is to add context — and it does: same ingestion pipeline as the primary path, returns parsed hand/tournament counts plus errors, and a negative scope statement ('does not grade solver frequencies'). It never explains why destructiveHint is true (e.g., whether a re-upload duplicates or overwrites data), which is the main remaining 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?

Three compact sentences with the most important routing fact ('Secondary upload path... Prefer get_upload_link') front-loaded. The sentence enumerating return fields is arguably redundant given an output schema exists, but nothing is padded.

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 not be spelled out, and annotations carry the safety profile; the description supplies the pipeline identity, the routing rule, and the solver-grading exclusion. Only the destructive semantics and any duplicate-upload behavior remain unaddressed.

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 description coverage is 100%, so both parameters (text, filename with its default) are already fully documented in the schema. The description adds only the vague size qualifier 'small paste' and no format guidance, so the baseline 3 is appropriate.

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') plus its role in the system ('secondary upload path for a small paste', 'runs the same ingestion pipeline'). It explicitly distinguishes itself from the sibling get_upload_link and the hosted /upload page, so the agent can tell them apart without opening schemas.

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?

Explicitly routes the agent to the preferred alternative ('Prefer get_upload_link and the hosted /upload page') and states the qualifying condition ('a small paste'). What is missing is a hard boundary — how small is 'small', and whether this path is ever required rather than merely discouraged.

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.