Charting: one match, every stat family
get_charting_matchEvery charting stat family for ONE charted match, both players, with the per-set split (set 1, set 2, ..., Total) exactly as charted. Charting ids are their own id space (1960 to 2026). Most of these matches have no counterpart in the live tables. Requires the ULTRA plan.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"charting_match_id": "<charting_match_id>"
},
"name": "get_charting_match"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| charting_match_id | Yes | Charting match id, in its own id space. Not a match_id. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | True when the request succeeded, including when the answer is an empty list. False for a missing or rejected key, a plan that does not include this data, an unknown id, a rate limit or a network error. The message then says what to do. check_api_status is the exception: it is true whenever the API answered, and reports API key problems in the message. | |
| gender | No | ||
| mcp_id | No | The charting dataset's own row identifier. | |
| message | Yes | Human-readable summary of the result, safe to relay to the user verbatim. | |
| players | No | Both players as charted. | |
| families | No | Every stat family, per player, with the per-set split. | |
| charting_match_id | No | The charted match. |