Match score
get_match_scoreCurrent score for one match. This is the fastest read, with the lowest latency. Use it when you only need the score and already know the match id. Works on the FREE plan (no card needed).
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": {
"match_id": "<match_id>"
},
"name": "get_match_score"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| match_id | Yes | Match id, as returned by get_live_matches, get_upcoming_matches or get_recent_results. |
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. | |
| score | No | The current score. | |
| message | Yes | Human-readable summary of the result, safe to relay to the user verbatim. |