Is it good enough?
This page is a projection of the one entry record, the Reliability factor that Use covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Capabilities & modalities
Text reasoning models (maths, coding, analysis) distilled from R1 onto Llama bases (8B, 70B). They emit explicit reasoning traces (think tags) and are strong for their size, the 70B especially.
Context window & long-context behaviour
The cards declare a 128K-token context. Effective long-context recall has not been measured, so treat 128K as the declared window.
Prompt format & chat template
The models follow the R1 reasoning / think-tag convention. Use apply_chat_template and
handle the reasoning segment at the client, either exposing or stripping it.
Language coverage
English is strongest (Llama base plus R1 distillation). Per-language depth varies with model size.
Function / tool calling
These are reasoning distils, and native structured tool-calling is not documented as a primary behaviour. Confirm per serving stack and size, and test.
Structured / JSON-constrained output
No model-documented native JSON or schema-constrained output guarantee exists. Constrained decoding is available at the serving layer (vLLM and SGLang grammars) as a runtime feature of the server.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
ReliabilityIs it reliable and good enough for the job?
StrongPerformance 3, operational 5 and safety 3: solid reasoning for the size and the broadest serving support of the distils. All three scores are at or above 3 and operational is 5, so reliability is strong. The gap is the absence of own safety tuning or a first-party guard model.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.