Draw probability for one match
get_draw_model[PAID] Every draw reading FDB4 holds for ONE match — use it when someone asks how likely a
specific fixture is to end level, rather than which teams are overdue a draw
(predict_draws answers that).
Five readings come back side by side, because they are not interchangeable: the Dixon-Coles goals model's own probability with the expected goals behind it; the historical draw rate at this fixture's Elo rating gap; the one-parameter blend of those two the site has published since September 2026; the five-feature logistic model that now sits beside it with a 95% band around it; and the bookmaker's draw price where one is recorded. Also returned: when the logistic model was last fitted, over how many matches, and its coefficients — so an answer can explain itself.
Identify the match by match_id, or by team (id or slug) plus an optional date;
with no date you get that team's next fixture. is_forecast says whether the
logistic figure is a real forecast (a fixture) or an in-sample description of a
match the model was fitted on. Historical pattern, not a betting tip.
Costs 1 point per call (1 point = 1 cent); paginated calls cost 1 point per page.
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_draw_model"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | With `team`, the match date as YYYY-MM-DD. Omit for that team's next fixture. | |
| team | No | A team id or slug (431, arsenal), from list_teams. Give this or `match_id`. | |
| match_id | No | The match id, from search_results or a fixture list. Give this or `team`. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |