Player hit rates
get_hit_ratesHow often one player has gone over, per stat, across their last graded games. Not on the Free plan: Free gets a 402 UPGRADE_REQUIRED with a few labelled sample rows and no credits charged; Developer and up read up to 100 graded games.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_hit_rates"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Game date | |
| last | No | Recent games | |
| stat | No | Machine stat slug | |
| after | No | Alias for cursor | |
| limit | No | Page size. Oversized valid limits are clamped. | |
| cursor | No | Cursor returned in meta.next_cursor | |
| league | No | Sport code | |
| player | No | Player name | |
| result | No | Outcome | |
| player_id | No | Public player id | |
| user_request | No | Optional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private. |