PokerData

Get the hand-upload link

get_upload_link

Read-onlyIdempotent

Primary hand-upload path. Returns https://pokerdata.io/upload on this origin, with a short-lived signed token for the caller's account when signing is configured. Hand the URL to the user. Pasting histories into chat is the fallback.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	URL to hand to the user, signed when signing is configured.
`primary`	No	Always true: this is the primary upload path.
`resource`	No	MCP resource URI that returns the same payload.
`expiresAt`	No	When the signed token expires, or null when unsigned.
`tokenAttached`	No	Whether the URL carries a signed token for this account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Hosted upload page for hand histories.",
+  "properties": {
+    "expiresAt": {
+      "description": "When the signed token expires, or null when unsigned.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "primary": {
+      "description": "Always true: this is the primary upload path.",
+      "type": "boolean"
+    },
+    "resource": {
+      "description": "MCP resource URI that returns the same payload.",
+      "type": "string"
+    },
+    "tokenAttached": {
+      "description": "Whether the URL carries a signed token for this account.",
+      "type": "boolean"
+    },
+    "url": {
+      "description": "URL to hand to the user, signed when signing is configured.",
+      "type": "string"
+    }
+  },
+  "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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description contributes real extra context beyond that: the token is short-lived, signed, tied to the caller's account, and only present 'when signing is configured.' It does not explain what happens when signing is absent.

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?

Four short sentences, front-loaded with the essential fact (this is the primary upload path) followed by return details and the action to take. 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-value documentation is not required, and the annotations carry the safety profile. The description covers purpose, returned URL, token behavior, and the fallback action. Missing only the edge case where signing is not configured.

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 the baseline is 4 and there is no parameter meaning to add. The description correctly focuses on output rather than inventing inputs.

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 outcome: returns the https://pokerdata.io/upload URL with a signed token for the caller's account. It is clear this is the link-acquisition tool and not the actual upload. It does not name the closest sibling (upload_hand_history) or explain the relationship, so it falls short of full sibling differentiation.

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?

Gives a clear directive: 'Hand the URL to the user,' and frames pasting histories into chat as 'the fallback,' which implies this link is the preferred path. No explicit when-not conditions or named alternatives among the sibling tools, but the usage context is unambiguous.

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?