Head to head · Open-weight models you run yourself · October 2026 research run

OTel-2.0-LLM-31B-IT vs Qwen3.8-27B

Qwen3.8-27B scores 68.6 (B) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on documentation and upkeep. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

OTel-2.0-LLM-31B-IT C

Best for Telecoms teams that want an open model for standards questions and RAG on their own hardware

Ahead on

  • Documentation and upkeep, 74 against 36

Watch for

BF16 only at 62.6 GB, with no GGUF or other quantised build from anyone we checked

Qwen3.8-27B B

Best for Agents that want a capable open model with vision on one 24 to 32 GB GPU or Mac, with the widest runtime support and a plain licence.

Ahead on

  • Reach, 90 against 50
  • Agent interface, 70 against 60

Watch for

No safety results, prompt-injection guidance or security contact

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reach Qwen3.8-27B +40

OTel-2.0-LLM-31B-IT 50

Memory 10, the publisher's only build is the BF16 safetensors, 62.55 GB for the 15 shards the index names, and 62.55 GB × 1.2 = 75.1 GB, above 64 GB and inside the reference machine's GPU share. Runtimes 15, the architecture is Gemma4ForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors files, three at 5 each. Builds 0, the publisher ships the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata, an OSI licence, with nothing added on the card. Download 10, gated is false on 10 November 2026, so the files download with no account or terms. Hosted 0, Hugging Face maps one inference provider, Featherless AI (live), short of the two the line needs. 10 + 15 + 0 + 15 + 10 + 0 = 50.

Qwen3.8-27B 90

Memory 25 of 30, Ollama's smallest 4-bit build is 18 GB, or 21.6 GB with a fifth added, which fits 24 GB. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang and Transformers all run the qwen3_5 architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, seven inference providers are live for it on Hugging Face on 1 November, though Qwen Cloud's own version is still described as coming soon.

Documentation and upkeep OTel-2.0-LLM-31B-IT +38

OTel-2.0-LLM-31B-IT 74

Model card 14, Intended use, a long limitations section, the architecture and training method, the parameters (31B) and the language (English) are on the card. Training data 15, the card names the sources (3GPP, ETSI, ITU, GSMA, CAMARA, O-RAN and TM Forum material provided by GSMA), the overall sizes (15 billion raw tokens, over 1 trillion processed, about 440 billion used), the mix of example types and the processing tool, and lists what was left out. Last change 20, the last commit, on 1 November 2026, updated the card's links, resources, citation and contacts, nine days before this check. Responsiveness 20, Of the 3 discussions that aren't pull requests (7 August to 28 October 2026), 2 have a reply from the repository's owner, which is most. Version policy 0, the weights were replaced in place: uploads on 27 July, 3 August and 1 September 2026 under one name, with a standing notice on the card that they may change and that users should pin a revision, and no dated note of what changed. File health 5, the card describes 15 shards of about 62.6 GB while the repository still holds an earlier 14-shard set beside them, 126.8 GB in all. 14 + 15 + 20 + 20 + 0 + 5 = 74.

Qwen3.8-27B 36

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, languages and a knowledge cut-off aren't. Training data 0, not described. Last change 15, the files last changed on 14 August 2026, 79 days before this check, and Qwen's GitHub repository for the model holds only a README and licence, so no reference code of Alibaba's changed later. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports, recounted on 1 November. Version policy 5, earlier 27B models stay in their own repositories without dated notes. File health 5, the files agree with the card but reports about the template and structured output wait without a reply.

Agent interface Qwen3.8-27B +10

OTel-2.0-LLM-31B-IT 60

Chat template 20, chat_template.jinja in the repository, 19,300 characters, the publisher's own. Tool-calling format 10, only the template says how tools are declared and how calls come back. Trained tool calling 20, the template loops over tool_calls, so it renders several calls in one turn, and the card says the training mix included general-purpose agentic tool-calling examples, while none were specific to telecoms. Structured output 0, the card doesn't document JSON or JSON Schema output. Reasoning control 0, the card says the model wasn't trained to produce or consume Gemma's thought channel and answers directly, so there is no thinking to switch or budget. Context 10, 262,144 positions in the text config, the base's native context. 20 + 10 + 20 + 0 + 0 + 10 = 60.

Qwen3.8-27B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10 of 25, the format lives only in the template and the parser name only in serving commands, Alibaba doesn't describe how tools are declared or returned. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented. Reasoning control 10, thinking turns off per request, reasoning_effort budgets it and the card shows the reasoning coming back in reasoning_content. Context 10, 262,144 tokens native.

Score by category

CategoryWeight this runOTel-2.0-LLM-31B-ITQwen3.8-27BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255090Qwen3.8-27B +40
Risk20%205555even
Agent interface10%106070Qwen3.8-27B +10
Documentation and upkeep10%107436OTel-2.0-LLM-31B-IT +38
Negative events≤1500
TotalC 56.8/100B 68.6/100

Facts side by side

FactOTel-2.0-LLM-31B-ITQwen3.8-27B
KindOpen-weight modelOpen-weight model
VendorAT&T (Open Telco AI)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-012026-08-14
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

OTel-2.0-LLM-31B-IT

A real telecoms post-training of Gemma 4 31B IT with an unusually candid card on what was and wasn't trained. It fits a 128 GB machine in BF16 only, with no quantised build, sits in a personal account, and its weights have been replaced in place. Tool-call format, structured output and safety results aren't documented.

Qwen3.8-27B

A dense cousin for coding and agent work with image and video input that runs almost anywhere. Ollama's 4-bit build needs about 22 GB, and seven providers host it for agents without the hardware. The main risk is that nobody at Alibaba answers, there are no safety results or agent guidance, and the tool format is only in the template.

Before you call either

OTel-2.0-LLM-31B-IT

  1. Download the 15 shards the index names, not the whole repository, which is twice the size
  2. Pin a revision. The card says the weights may change under the same name
  3. Serve it with vLLM 0.19.0 or later and the repository's own chat template, not Gemma 4's
  4. Send no thinking flags. It answers directly and wasn't trained on Gemma's thought channel
  5. Use it as the generation stage of a RAG pipeline over telecom standards, with source attribution and human review
  6. Don't use it to run network tools unattended. The card says that hasn't been evaluated

Qwen3.8-27B

  1. Quickest start is ollama run qwen3.8, about 18 GB of files
  2. On our reference machine use BF16 with vllm serve Qwen/Qwen3.8-27B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, since FP8 on gfx1151 isn't documented
  3. Use the qwen3_coder tool parser, SGLang's cookbook says the Hermes parser leaves its calls unparsed
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks, and read the reasoning from reasoning_content
  5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
  6. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
  7. Preserved thinking keeps earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
  8. Turn on YaRN only beyond 262,144 tokens, the card warns static YaRN can cost quality on short texts
  9. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Questions

Which is better for AI agents, OTel-2.0-LLM-31B-IT or Qwen3.8-27B?

Qwen3.8-27B scores 68.6 (B) on agent readiness against OTel-2.0-LLM-31B-IT's 56.8 (C), and leads in 2 of 4 scored categories. OTel-2.0-LLM-31B-IT leads on documentation and upkeep.

Other comparisons with OTel-2.0-LLM-31B-IT or Qwen3.8-27B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.