Answer
Asked during eval run step19-smoke-gpt-oss-120b-cloud · case unsupported-wildcard-value · snapshot GW9
Question
Check the chip-value tool using the full model for GW9 only. Can it calculate the expected points gain from playing my Wildcard?
Answer
completed trace 43fccac9Result of the chip‑value query (snapshot 28 Oct 2026, target GW 9, “full” model)
| GW | your XI | Triple Captain | Bench Boost | Free Hit |
|---|---|---|---|---|
| 9 | 45.61 pts | +5.88 pts | +5.24 pts | +7.90 pts |
The response also lists the chips that are still available to you:
- Wildcard (until GW 19)
- Free‑Hit (until GW 19)
- Bench‑Boost (until GW 19)
- Triple‑Captain (until GW 19)
Why there is no “Wildcard” entry
The get_chip_values tool only returns point‑gain estimates for chips that directly add points on top of the already‑optimised XI (Triple‑Captain, Bench‑Boost, Free‑Hit).
A Wildcard does not give extra points; it simply allows you to change your squad without incurring transfer hits. Because its effect is a change in squad composition rather than a point multiplier, the tool does not calculate a separate “expected points gain” for it.
What to do if you want to assess the Wildcard’s impact
To see how a Wildcard would affect your projected points you need a tool that re‑optimises the squad under the Wildcard assumption, such as get_recommendation (with max_hits = 0 and the Wildcard chip marked as available). That will show the projected XI points after the squad change and let you compare them with the current “your XI” value (45.61 pts for GW 9).
Bottom line
The chip‑value tool can give you the expected point boost for Triple‑Captain, Bench‑Boost and Free‑Hit, but it does not calculate a point‑gain figure for playing your Wildcard. Use a squad‑optimisation/recommendation query to evaluate the benefit of a Wildcard for GW 9.
Run
- Status
- completed
- Target gameweek
- GW9
- Model
- gpt-oss:120b-cloud
- Temperature
- 0
- Model calls
- 2 of 4
- Tool calls
- 1
- Latency
- 4.7 s
- Tokens
- 2,739 in · 785 out
- Snapshot ID
- 20261028_212650_step17-current_3a1d9408-dirty
Checks
-
Tool selectionpass
-
Argumentspass
-
Numberspass
-
Teamsn/a
-
Safetyn/a
Tool calls
{
"horizon": 1,
"model": "full"
}
Result fields: snapshot_id, as_of, season, target_gw, model, values, best_gws, available_chips, assumptions. Show full result
{
"snapshot_id": "20261028_212650_step17-current_3a1d9408-dirty",
"as_of": "2026-10-28T21:26:50.640392Z",
"season": "2026-27",
"target_gw": 9,
"model": "full",
"values": [
{
"gw": 9,
"your_xi": 45.60745605684265,
"triple_captain": 5.880235614972674,
"bench_boost": 5.236402849718311,
"free_hit": 7.9002174202812725
}
],
"best_gws": {
"triple_captain": 9,
"bench_boost": 9,
"free_hit": 9
},
"available_chips": [
"wildcard (until GW19)",
"freehit (until GW19)",
"bboost (until GW19)",
"3xc (until GW19)"
],
"assumptions": [
"Uses the current frozen squad in every GW; future transfers are not planned.",
"Values are hypothetical gains even for chips that are no longer available.",
"The existing optimiser includes its default bench weight in squad selection.",
"For equal chip values, best_gws selects the earliest GW."
]
}