Head to head · Open-weight models you run yourself · October 2026 research run
LFM3-Omni-2B vs Qwen3.8-Flash-Next
Qwen3.8-Flash-Next and LFM3-Omni-2B score within a point of each other on agent readiness, 61.8 (C) and 61 (C). LFM3-Omni-2B leads on reach and documentation and upkeep. Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 4969 open weights comparisons
Which one, for what
Best for Voice and camera agents on a laptop or phone that want one small model for hearing, seeing, speaking and calling tools
Ahead on
- Reach, 80 against 65
- Documentation and upkeep, 49 against 36
Watch for
Only llama.cpp and Ollama run it in a release
Best for Teams with a multi-GPU server or a 128 GB Mac who want Qwen's newest sparse architecture for agentic coding and multimodal work, and aren't a hosted-model or coding-assistant business.
Ahead on
- Risk, 45 against 40
Watch for
No build fits the reference machine's 107.4 GB, and Ollama's smallest Linux build is 120 GB
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 LFM3-Omni-2B +15
LFM3-Omni-2B 80
Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.29 GB projector file, and 1.39 GB × 1.2 = 1.7 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 vision and audio projectors and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example), and Ollama's library has an lfm3-omni entry. Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-omni-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.
Qwen3.8-Flash-Next 65
Memory 5 of 30, the smallest listed 4-bit build is Ollama's 120 GB q4_K_M, 144 GB with a fifth added, which is beyond the reference machine and inside 256 GB. Ollama's Apple-only 105 GB MLX build isn't among the builds and would land in the same band. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang and Transformers all run the qwen4_exp architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 10 of 15, a custom licence that's free for commercial use except for model-as-a-service and coding or office assistant businesses, which need a separate licence. Download 10, neither repository is gated. Hosted 5, Hugging Face lists two live providers, Featherless AI for the BF16 repository and Nscale for the FP8 build, and Alibaba's Qwen Cloud serves Qwen3.8-Flash, which the card says is based on these weights.
Documentation and upkeep LFM3-Omni-2B +13
LFM3-Omni-2B 49
Model card 14, Intended use (one on-device model in place of separate speech recognition, vision, language and speech models), architecture, parameters (2.17B), context (32K) and the text and speech languages. Training data 5, the card has no training section. Last change 20, the last commit, on 3 November 2026, changed the card's navigation icons, seven days before this check, and the one before it, on 28 October, documented video frame rate and frame limits. Responsiveness 0, none of the 12 discussions that aren't pull requests (27 October to 9 November 2026) has a reply from a LiquidAI member. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 5, the card gives a 32K context while config.json gives the language model 128,000 positions and Liquid's API lists 128,000 for the hosted model, so the card and the files don't agree on context. 14 + 5 + 20 + 0 + 5 + 5 = 49.
Qwen3.8-Flash-Next 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 beyond a token count relative to an earlier model. Last change 15, the FP8 config fix on 31 August 2026, 63 days before 2 November. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports (29 to 79, 27 August to 26 October), its only reply came in the first week. Version policy 5, a first release with nothing replaced. File health 5, the files agree with the card, but a 19 October report about the template and a pull request to fix it still wait without a reply. 11 + 0 + 15 + 0 + 5 + 5 = 36.
Risk Qwen3.8-Flash-Next +5
LFM3-Omni-2B 40
File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.
Qwen3.8-Flash-Next 45
File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, and every file has a checksum. Safety evaluation 0, none published on the card or in the technical report. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 5 of 15, 5 off for the field-of-use limit on model-as-a-service and coding or office assistant businesses and 5 off for the naming duty above a user or revenue threshold. Security programme 0, no security.txt, disclosure policy or security contact for Qwen was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent.
Score by category
| Category | Weight this run | LFM3-Omni-2B | Qwen3.8-Flash-Next | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 80 | 65 | LFM3-Omni-2B +15 |
| Risk | 20%20 | 40 | 45 | Qwen3.8-Flash-Next +5 |
| Agent interface | 10%10 | 70 | 70 | even |
| Documentation and upkeep | 10%10 | 49 | 36 | LFM3-Omni-2B +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 61.8/100 |
Facts side by side
| Fact | LFM3-Omni-2B | Qwen3.8-Flash-Next |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Liquid AI | Alibaba (Qwen team) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | LFM Open License v1.0 (free commercial use below $10M annual revenue) | Qwen Community License 1.0 (custom, not an OSI licence). Free of charge, the model name shown in products above 100M monthly users or US$20M monthly revenue, and a separate licence from Qwen before commercial use by a Model as a Service or AI Work Assistant business |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-03 | 2026-08-31 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 2/5 (4) |
Verdicts
LFM3-Omni-2B
One 2.17B model that sees, listens and talks on an 8 GB machine and turns spoken requests into tool calls. Only llama.cpp and Ollama run it in a release. The context is 32K, it doesn't reason, Liquid hasn't answered a question on the repository, and there are no safety results or data sources.
Qwen3.8-Flash-Next
A large sparse cousin with 6B active parameters for agentic coding and multimodal work, previewing Qwen's next architecture. It needs a 128 GB Mac for Ollama's MLX build or about 144 GB for the 4-bit GGUF, and Qwen Cloud serves it. The main risk is a licence that needs a separate deal for hosted-model and coding or office assistant businesses.
Before you call either
LFM3-Omni-2B
- Start it with
llama-server -hf LiquidAI/LFM3-Omni-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-omni - Greedy decoding for text. For speech use audio_temperature 0.4 and audio_repetition_penalty 1.2, per the card
- The context is 32K, and llama.cpp samples video at 2 frames a second up to 384 frames
- Parse tool calls yourself from the XML it returns
- It doesn't reason, so don't pass enable_thinking
- Validate JSON output yourself
Qwen3.8-Flash-Next
- On a 128 GB Mac start it with
ollama run qwen3.8-flash-next:125b-mlx(105 GB, NVFP4), on Linux the smallest Ollama build isqwen3.8-flash-next:125b-a6b-q4_K_Mat 120 GB, which won't fit a 107.4 GB GPU share - On a server,
vllm serve Qwen/Qwen3.8-Flash-Next-FP8 --tensor-parallel-size 4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder - Use the qwen3_coder tool parser and the qwen3 reasoning parser, as Qwen's GitHub README does
- Thinking is on by default, pass
chat_template_kwargswithenable_thinkingfalse to skip it, and read the reasoning fromreasoning_content, even though SGLang's cookbook says thinking can't be turned off reasoning_efforttakes xhigh (default), medium or low, and any other value makes the template raise an error- Send at most one system message and put it first, since the template raises an error otherwise
- 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
- vLLM keeps the 51B n-gram table in host memory on 80 GB GPUs by default, per its recipe
- Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
- Read the Qwen Community License before serving it to others as an API or inside a coding or office assistant product
Questions
Which is better for AI agents, LFM3-Omni-2B or Qwen3.8-Flash-Next?
Qwen3.8-Flash-Next and LFM3-Omni-2B score within a point of each other on agent readiness, 61.8 (C) and 61 (C). LFM3-Omni-2B leads on reach and documentation and upkeep.
Other comparisons with LFM3-Omni-2B or Qwen3.8-Flash-Next
- Agents-A1-4B vs LFM3-Omni-2B
- Agents-A1-4B vs Qwen3.8-Flash-Next
- Apertus v1.5 8B vs LFM3-Omni-2B
- Apertus v1.5 8B vs Qwen3.8-Flash-Next
- Apodex-1.1-mini vs LFM3-Omni-2B
- Apodex-1.1-mini vs Qwen3.8-Flash-Next
- Arete-27B vs LFM3-Omni-2B
- Arete-27B vs Qwen3.8-Flash-Next
- BigBang-v1 vs LFM3-Omni-2B
- BigBang-v1 vs Qwen3.8-Flash-Next
- Carbon-X vs LFM3-Omni-2B
- Carbon-X vs Qwen3.8-Flash-Next
- Cosmos-Reason2-2B vs LFM3-Omni-2B
- Cosmos-Reason2-2B vs Qwen3.8-Flash-Next
- Darwin-36B-Opus vs LFM3-Omni-2B
- Darwin-36B-Opus vs Qwen3.8-Flash-Next
- DeepSeek-V3.2 vs LFM3-Omni-2B
- DeepSeek-V3.2 vs Qwen3.8-Flash-Next
- DeepSeek V4.1 Flash vs LFM3-Omni-2B
- DeepSeek V4.1 Flash vs Qwen3.8-Flash-Next
- DeepSeek-V4-Flash-0731 vs LFM3-Omni-2B
- DeepSeek-V4-Flash-0731 vs Qwen3.8-Flash-Next
- DiffusionGemma 26B A4B IT vs LFM3-Omni-2B
- DiffusionGemma 26B A4B IT vs Qwen3.8-Flash-Next
- Gemma 4 12B IT vs LFM3-Omni-2B
- Gemma 4 12B IT vs Qwen3.8-Flash-Next
- Gemma 4 26B A4B IT vs LFM3-Omni-2B
- Gemma 4 26B A4B IT vs Qwen3.8-Flash-Next
- Gemma 4 31B IT vs LFM3-Omni-2B
- Gemma 4 31B IT vs Qwen3.8-Flash-Next
- Gemma 4 E2B IT vs LFM3-Omni-2B
- Gemma 4 E2B IT vs Qwen3.8-Flash-Next
- Gemma 4 E4B IT vs LFM3-Omni-2B
- Gemma 4 E4B IT vs Qwen3.8-Flash-Next
- GLM-4.5-Air vs LFM3-Omni-2B
- GLM-4.5-Air vs Qwen3.8-Flash-Next
- GLM-4.7-Flash vs LFM3-Omni-2B
- GLM-4.7-Flash vs Qwen3.8-Flash-Next
- GLM-5.3-Flash vs LFM3-Omni-2B
- GLM-5.3-Flash vs Qwen3.8-Flash-Next
- GLM-5.3 vs LFM3-Omni-2B
- GLM-5.3 vs Qwen3.8-Flash-Next
- gpt-oss-120b vs LFM3-Omni-2B
- gpt-oss-120b vs Qwen3.8-Flash-Next
- gpt-oss-20b vs LFM3-Omni-2B
- gpt-oss-20b vs Qwen3.8-Flash-Next
- Granite 4.2 30B vs LFM3-Omni-2B
- Granite 4.2 30B vs Qwen3.8-Flash-Next
- Granite 4.2 3B vs LFM3-Omni-2B
- Granite 4.2 3B vs Qwen3.8-Flash-Next
- Granite 4.2 8B vs LFM3-Omni-2B
- Granite 4.2 8B vs Qwen3.8-Flash-Next
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs Qwen3.8-Flash-Next
- Hy3 vs LFM3-Omni-2B
- Hy3 vs Qwen3.8-Flash-Next
- Inkling-Small vs LFM3-Omni-2B
- Inkling-Small vs Qwen3.8-Flash-Next
- Inkling vs LFM3-Omni-2B
- Inkling vs Qwen3.8-Flash-Next
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-Omni-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Qwen3.8-Flash-Next
- Kimi K3.1 Pro vs LFM3-Omni-2B
- Kimi K3.1 Pro vs Qwen3.8-Flash-Next
- Kimi K3 vs LFM3-Omni-2B
- Kimi K3 vs Qwen3.8-Flash-Next
- Kolibri-1 vs LFM3-Omni-2B
- Kolibri-1 vs Qwen3.8-Flash-Next
- Kronos vs LFM3-Omni-2B
- Kronos vs Qwen3.8-Flash-Next
- Laguna M.1 vs LFM3-Omni-2B
- Laguna M.1 vs Qwen3.8-Flash-Next
- Laguna S 2.1 vs LFM3-Omni-2B
- Laguna S 2.1 vs Qwen3.8-Flash-Next
- Laguna XS 2.1 vs LFM3-Omni-2B
- Laguna XS 2.1 vs Qwen3.8-Flash-Next
- LBS-27B vs LFM3-Omni-2B
- LBS-27B vs Qwen3.8-Flash-Next
- LFM2.5-2.6B vs LFM3-Omni-2B
- LFM2.5-2.6B vs Qwen3.8-Flash-Next
- LFM3-1.7B vs LFM3-Omni-2B
- LFM3-1.7B vs Qwen3.8-Flash-Next
- LFM3-Audio-2B vs LFM3-Omni-2B
- LFM3-Audio-2B vs Qwen3.8-Flash-Next
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs Ling-3.0-tiny
- LFM3-Omni-2B vs Ling-3.1-flash-1019
- LFM3-Omni-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-Omni-2B vs MiniCPM-o 4.5
- LFM3-Omni-2B vs MiniCPM-V 4.7 1B
- LFM3-Omni-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-Omni-2B vs MiniCPM5-2B
- LFM3-Omni-2B vs MiniMax-M2.5
- LFM3-Omni-2B vs MiniMax-M2.7
- LFM3-Omni-2B vs MiniMax-M3.1-Flash
- LFM3-Omni-2B vs Mistral Large 4
- LFM3-Omni-2B vs Muse Glimmer 30B
- LFM3-Omni-2B vs Nanbeige4.3-33B
- LFM3-Omni-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-Omni-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 4B
- LFM3-Omni-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-Omni-2B vs Nemotron 3 Super 120B A12B
- LFM3-Omni-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-Omni-2B vs occamy-1.0
- LFM3-Omni-2B vs Olmo 3 7B Think
- LFM3-Omni-2B vs Ornith-1.5-122B
- LFM3-Omni-2B vs Ornith-1.5-35B-A3B
- LFM3-Omni-2B vs Ornith-1.5-397B
- LFM3-Omni-2B vs Ornith-1.5-9B
- LFM3-Omni-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-Omni-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-Omni-2B vs Qwen3-4B-Instruct-2507
- LFM3-Omni-2B vs Qwen3.5-0.8B
- LFM3-Omni-2B vs Qwen3.5-122B-A10B
- LFM3-Omni-2B vs Qwen3.5-2B
- LFM3-Omni-2B vs Qwen3.5-397B-A17B
- LFM3-Omni-2B vs Qwen3.5-4B
- LFM3-Omni-2B vs Qwen3.5-9B
- LFM3-Omni-2B vs Qwen3.6-27B
- LFM3-Omni-2B vs Qwen3.6-35B-A3B
- LFM3-Omni-2B vs Qwen3.8-27B
- LFM3-Omni-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-Coder-Next
- LFM3-Omni-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-2B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-32B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-4B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-8B-Instruct
- LFM3-Omni-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-Omni-2B vs Recursive Flint
- LFM3-Omni-2B vs Ripple-65B Preview
- LFM3-Omni-2B vs SmolLM3-3B
- LFM3-Omni-2B vs Spark-X2.6-4B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-Omni-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-Omni-2B vs Baidu Unlimited-OCR-2
- LFM3-VL-2B vs Qwen3.8-Flash-Next
- Ling-3.0-tiny vs Qwen3.8-Flash-Next
- Ling-3.1-flash-1019 vs Qwen3.8-Flash-Next
- MiMo-V2.6 Distill Qwen 9B vs Qwen3.8-Flash-Next
- MiniCPM-o 4.5 vs Qwen3.8-Flash-Next
- MiniCPM-V 4.7 1B vs Qwen3.8-Flash-Next
- MiniCPM-V 4.7 35B-A3B vs Qwen3.8-Flash-Next
- MiniCPM5-2B vs Qwen3.8-Flash-Next
- MiniMax-M2.5 vs Qwen3.8-Flash-Next
- MiniMax-M2.7 vs Qwen3.8-Flash-Next
- MiniMax-M3.1-Flash vs Qwen3.8-Flash-Next
- Mistral Large 4 vs Qwen3.8-Flash-Next
- Muse Glimmer 30B vs Qwen3.8-Flash-Next
- Nanbeige4.3-33B vs Qwen3.8-Flash-Next
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs Qwen3.8-Flash-Next
- Nemotron 3.5 Lightning 30B A3B vs Qwen3.8-Flash-Next
- Nemotron 3 Nano 30B A3B vs Qwen3.8-Flash-Next
- Nemotron 3 Nano 4B vs Qwen3.8-Flash-Next
- Nemotron 3 Nano Omni 30B A3B Reasoning vs Qwen3.8-Flash-Next
- Nemotron 3 Super 120B A12B vs Qwen3.8-Flash-Next
- Nemotron 3 Ultra 550B A55B vs Qwen3.8-Flash-Next
- occamy-1.0 vs Qwen3.8-Flash-Next
- Olmo 3 7B Think vs Qwen3.8-Flash-Next
- Ornith-1.5-122B vs Qwen3.8-Flash-Next
- Ornith-1.5-35B-A3B vs Qwen3.8-Flash-Next
- Ornith-1.5-397B vs Qwen3.8-Flash-Next
- Ornith-1.5-9B vs Qwen3.8-Flash-Next
- Qwen-AgentWorld-35B-A3B vs Qwen3.8-Flash-Next
- Qwen3-30B-A3B-Instruct-2507 vs Qwen3.8-Flash-Next
- Qwen3-4B-Instruct-2507 vs Qwen3.8-Flash-Next
- Qwen3.5-0.8B vs Qwen3.8-Flash-Next
- Qwen3.5-122B-A10B vs Qwen3.8-Flash-Next
- Qwen3.5-2B vs Qwen3.8-Flash-Next
- Qwen3.5-397B-A17B vs Qwen3.8-Flash-Next
- Qwen3.5-4B vs Qwen3.8-Flash-Next
- Qwen3.5-9B vs Qwen3.8-Flash-Next
- Qwen3.6-27B vs Qwen3.8-Flash-Next
- Qwen3.6-35B-A3B vs Qwen3.8-Flash-Next
- Qwen3.8-27B vs Qwen3.8-Flash-Next
- Qwen3.8-Flash-Next vs Qwen3-Coder-30B-A3B-Instruct
- Qwen3.8-Flash-Next vs Qwen3-Coder-Next
- Qwen3.8-Flash-Next vs Qwen3-Omni-30B-A3B-Instruct
- Qwen3.8-Flash-Next vs Qwen3-VL-2B-Instruct
- Qwen3.8-Flash-Next vs Qwen3-VL-30B-A3B-Instruct
- Qwen3.8-Flash-Next vs Qwen3-VL-32B-Instruct
- Qwen3.8-Flash-Next vs Qwen3-VL-4B-Instruct
- Qwen3.8-Flash-Next vs Qwen3-VL-8B-Instruct
- Qwen3.8-Flash-Next vs Qwopus3.8-27B-Flash-V2
- Qwen3.8-Flash-Next vs Recursive Flint
- Qwen3.8-Flash-Next vs Ripple-65B Preview
- Qwen3.8-Flash-Next vs SmolLM3-3B
- Qwen3.8-Flash-Next vs Spark-X2.6-4B
- Qwen3.8-Flash-Next vs Swift 1.5 Qwen3.8-27B
- Qwen3.8-Flash-Next vs Swift 1.5 Qwen3.8-Flash-Next
- Qwen3.8-Flash-Next vs ThinkingCap (Qwen3.8 27B)
- Qwen3.8-Flash-Next vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/lfm3-omni-2b-vs-qwen3-8-flash-next.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm3-omni-2b.json·/api/v1/tools/qwen3-8-flash-next.json - From a terminal
anchor compare lfm3-omni-2b qwen3-8-flash-next(the CLI) - Over MCP
compare_tools {"a": "lfm3-omni-2b", "b": "qwen3-8-flash-next"}at/mcp, no key