Head to head · Open-weight models you run yourself · October 2026 research run
LFM3-VL-2B vs Muse Glimmer 30B
Muse Glimmer 30B scores 70 (BB) on agent readiness against LFM3-VL-2B's 61 (C), and leads in 2 of 4 scored categories. LFM3-VL-2B leads on agent interface 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 Agents on a laptop, phone or robot that need to read screens, documents, images and video from a model under 2 GB at 4 bits
Ahead on
- Agent interface, 90 against 75
- Documentation and upkeep, 77 against 65
Watch for
vLLM and SGLang support is unreleased, which the card says itself
Best for Local agents and coding with image input on one 24 to 32 GB GPU or an Apple silicon laptop, where one tool call per turn is enough
Ahead on
- Reach, 90 against 85
- Risk, 80 against 40
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
One tool call per turn and no parallel calls
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.
Risk Muse Glimmer 30B +40
LFM3-VL-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.
Muse Glimmer 30B 80
File safety 25, safetensors and GGUF, with the ExecuTorch pos_embed.bin files read as raw embedding tables by their exact size and the Hub's scans, and no repository code runs. Provenance 15, the verified meta-models organisation Meta links, with a checksum on every file. Safety evaluation 10, Meta's own published results with stated set-ups but nothing to rerun and no outside assessor. Agent guidance 15, trained against indirect prompt injection with a principal hierarchy, and results published. Licence risk 10, 5 off for the use policy, and the policy's pointer to a latest copy leads back to the same repository file with no change clause. Security programme 5, a whitehat route in the usage policy, with no security.txt and public advisories unchecked, so scored as absent.
Agent interface LFM3-VL-2B +15
LFM3-VL-2B 90
Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, images and video, tools, deferred tools, tool results and the thinking switch. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card says its fine-tuning mix included tool calling and agentic traces. Structured output 5, the card's vLLM and SGLang commands set a structured-output backend and its fine-tuning table has a JSON extraction notebook, but nothing says how to ask this model for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, Liquid's chat-template page documents enable_thinking=False in apply_chat_template for LFM3, with reasoning on by default inside think tags, and the card documents preserve_thinking and reports a no-thinking configuration in its benchmarks. Context 10, 128K tokens of input and output per the card, and max_position_embeddings 128000 for the language model in config.json. 20 + 25 + 20 + 5 + 10 + 10 = 90.
Muse Glimmer 30B 75
Chat template 20, a Jinja file in the repository. Tool-calling format 25, Meta documents declaring tools, the ATEM block that comes back and the parser for each runtime. Trained tool calling 10, one call per turn and no parallel calls. Structured output 0, nothing documented for JSON or JSON Schema. Reasoning control 10, reasoning can't be turned off but is budgeted per request with four strength levels and returned as reasoning_content. Context 10, 131,072 tokens trained in.
Documentation and upkeep LFM3-VL-2B +12
LFM3-VL-2B 77
Model card 17, Intended use (questions about video, documents, charts and app screens, finding objects, spatial reasoning), a limitation (not recommended for coding, multi-turn conversations or complex reasoning), architecture (language model, 14-layer vision encoder and projector), parameters (1.92B), context (128K) and 16 languages. Training data 5, A general description: the base's 22T tokens of pre-training with the kinds of data added since LFM2, then vision mid-training on image and video data, supervised fine-tuning, vision reinforcement learning and distillation. Last change 20, the last commit, on 9 November 2026, added the OpenVINO checkpoint to the card's inference table, a day before this check. Responsiveness 20, Of the 5 discussions that aren't pull requests (27 to 31 October 2026), 3 have a reply from a LiquidAI member, which is most. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 10, Config, template and card agree on the lfm3_vl architecture, the 128,000-token context and the vision settings in processor_config.json. 17 + 5 + 20 + 20 + 5 + 10 = 77.
Muse Glimmer 30B 65
Model card 20, all seven parts present, languages as a count of more than 100. Training data 10, a general description with a 4 January 2026 cut-off and no sources or sizes. Last change 20, a card update on 20 October citing the technical report, read as a change to the files as card edits were for other listings; Meta added its own MMI evaluation results file on 22 October. Responsiveness 5, a Meta member replied to 1 of the 40 most recent non-PR discussions (re-counted on 1 November). Version policy 5, a first release. File health 5, the files agree but a chat template bug report from 11 August still has no reply.
Reach Muse Glimmer 30B +5
LFM3-VL-2B 85
Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.20 GB projector file, and 1.30 GB × 1.2 = 1.6 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 15, Released llama.cpp has the lfm3 architecture and the LFM3-VL projector (src/models/lfm3.cpp and tools/mtmd at b12242), Ollama's library has an lfm3-vl entry, and LM Studio's catalogue lists liquid/lfm3-vl-2b. 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-vl-2b among its models, so the publisher hosts it. 30 + 15 + 15 + 10 + 10 + 5 = 85.
Muse Glimmer 30B 90
Memory 25, Meta's 16.8 GB Q4_K_M GGUF needs about 20 GB with the runtime's fifth, so it fits a 24 GB card but not 16 GB. Runtimes 25, released model code in vLLM, SGLang, Transformers, llama.cpp and Ollama's library fills the cap. Builds 15, Meta publishes GGUF and ExecuTorch 4-bit builds, read as two kinds as gemma-4-31b-it was, though all are 4-bit k-quants. Terms 10, Apache 2.0 with a usage policy that adds limits beyond the law, so a free commercial licence under a use policy. Download 10, no repository is gated. Hosted 5, Meta's API doesn't serve it but Together, Featherless AI and DeepInfra are live on its Hub page.
Score by category
| Category | Weight this run | LFM3-VL-2B | Muse Glimmer 30B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 85 | 90 | Muse Glimmer 30B +5 |
| Risk | 20%20 | 40 | 80 | Muse Glimmer 30B +40 |
| Agent interface | 10%10 | 90 | 75 | LFM3-VL-2B +15 |
| Documentation and upkeep | 10%10 | 77 | 65 | LFM3-VL-2B +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | BB 70/100 |
Facts side by side
| Fact | LFM3-VL-2B | Muse Glimmer 30B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Liquid AI | Meta |
| 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) | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-09 | 2026-10-20 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 3.8/5 (4) |
Verdicts
LFM3-VL-2B
A 1.92B vision model that reads images and video on an 8 GB machine, with a documented tool-call format and thinking. It runs today in llama.cpp, Ollama and LM Studio, while vLLM and SGLang support is still unreleased. Transformers needs repository code, and there are no safety results, security contact or data sources.
Muse Glimmer 30B
A dense 30B multimodal cousin for local agent and coding work with images, documented tool calls and adjustable reasoning. Meta's 17 GB GGUF fits a 24 GB card and runs in llama.cpp, Ollama, vLLM, SGLang and Transformers. The main risks are one tool call per turn, no documented JSON output and a usage policy that adds limits to Apache 2.0.
Before you call either
LFM3-VL-2B
- Start it with
llama-server -hf LiquidAI/LFM3-VL-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-vl, with llama.cpp b11960 or later - Use temperature 0.1, top_k 50 and repetition penalty 1.1, per the card
- Video is sampled at 2 frames a second up to 768 frames, and each frame costs context. Video input in llama.cpp needs ffmpeg
- Don't plan on vLLM or SGLang until a release carries LFM3-VL
- Validate JSON output yourself
- Liquid doesn't recommend it for coding, multi-turn conversations or complex reasoning
Muse Glimmer 30B
- Start it with
llama serve -hf meta-models/Muse-Glimmer-30B-GGUF --hf-file Muse-Glimmer-30B-KQuant-17GB-Q4_K_M.gguf -ngl 99 -c 131072 --host 127.0.0.1 --port 8080 --chat-template-kwargs '{"reasoning_strength":"high"}'on llama.cpp b10353 or later, orollama run muse-glimmeron Ollama 0.32.7 or later - In vLLM pass
--tool-call-parser muse_glimmer --reasoning-parser muse_glimmer, in SGLangmusefor both, in ExecuTorch--tool-parser atem. Without them tool calls come back as plain text - Set reasoning per request with
chat_template_kwargs.reasoning_strength(low, medium, high or xhigh). llama.cpp and ExecuTorch don't readreasoning_effort, and ExecuTorch rejects it with a 400 - Expect one tool call per turn and return each result before the next. ExecuTorch's server rejects
tool_choice="required" - Keep temperature 1.0, top_p 0.95 and top_k 64, don't run greedy, and never stop on
<|eom|> - Leave max_tokens room for reasoning, since in llama.cpp a request cut off mid-thought returns empty content with finish_reason length
- For images add Meta's 1.4 GB mmproj GGUF, which takes the build to about 22 GB with the runtime's fifth
Questions
Which is better for AI agents, LFM3-VL-2B or Muse Glimmer 30B?
Muse Glimmer 30B scores 70 (BB) on agent readiness against LFM3-VL-2B's 61 (C), and leads in 2 of 4 scored categories. LFM3-VL-2B leads on agent interface and documentation and upkeep.
Other comparisons with LFM3-VL-2B or Muse Glimmer 30B
- Agents-A1-4B vs LFM3-VL-2B
- Agents-A1-4B vs Muse Glimmer 30B
- Apertus v1.5 8B vs LFM3-VL-2B
- Apertus v1.5 8B vs Muse Glimmer 30B
- Apodex-1.1-mini vs LFM3-VL-2B
- Apodex-1.1-mini vs Muse Glimmer 30B
- Arete-27B vs LFM3-VL-2B
- Arete-27B vs Muse Glimmer 30B
- BigBang-v1 vs LFM3-VL-2B
- BigBang-v1 vs Muse Glimmer 30B
- Carbon-X vs LFM3-VL-2B
- Carbon-X vs Muse Glimmer 30B
- Cosmos-Reason2-2B vs LFM3-VL-2B
- Cosmos-Reason2-2B vs Muse Glimmer 30B
- Darwin-36B-Opus vs LFM3-VL-2B
- Darwin-36B-Opus vs Muse Glimmer 30B
- DeepSeek-V3.2 vs LFM3-VL-2B
- DeepSeek-V3.2 vs Muse Glimmer 30B
- DeepSeek V4.1 Flash vs LFM3-VL-2B
- DeepSeek V4.1 Flash vs Muse Glimmer 30B
- DeepSeek-V4-Flash-0731 vs LFM3-VL-2B
- DeepSeek-V4-Flash-0731 vs Muse Glimmer 30B
- DiffusionGemma 26B A4B IT vs LFM3-VL-2B
- DiffusionGemma 26B A4B IT vs Muse Glimmer 30B
- Gemma 4 12B IT vs LFM3-VL-2B
- Gemma 4 12B IT vs Muse Glimmer 30B
- Gemma 4 26B A4B IT vs LFM3-VL-2B
- Gemma 4 26B A4B IT vs Muse Glimmer 30B
- Gemma 4 31B IT vs LFM3-VL-2B
- Gemma 4 31B IT vs Muse Glimmer 30B
- Gemma 4 E2B IT vs LFM3-VL-2B
- Gemma 4 E2B IT vs Muse Glimmer 30B
- Gemma 4 E4B IT vs LFM3-VL-2B
- Gemma 4 E4B IT vs Muse Glimmer 30B
- GLM-4.5-Air vs LFM3-VL-2B
- GLM-4.5-Air vs Muse Glimmer 30B
- GLM-4.7-Flash vs LFM3-VL-2B
- GLM-4.7-Flash vs Muse Glimmer 30B
- GLM-5.3-Flash vs LFM3-VL-2B
- GLM-5.3-Flash vs Muse Glimmer 30B
- GLM-5.3 vs LFM3-VL-2B
- GLM-5.3 vs Muse Glimmer 30B
- gpt-oss-120b vs LFM3-VL-2B
- gpt-oss-120b vs Muse Glimmer 30B
- gpt-oss-20b vs LFM3-VL-2B
- gpt-oss-20b vs Muse Glimmer 30B
- Granite 4.2 30B vs LFM3-VL-2B
- Granite 4.2 30B vs Muse Glimmer 30B
- Granite 4.2 3B vs LFM3-VL-2B
- Granite 4.2 3B vs Muse Glimmer 30B
- Granite 4.2 8B vs LFM3-VL-2B
- Granite 4.2 8B vs Muse Glimmer 30B
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs Muse Glimmer 30B
- Hy3 vs LFM3-VL-2B
- Hy3 vs Muse Glimmer 30B
- Inkling-Small vs LFM3-VL-2B
- Inkling-Small vs Muse Glimmer 30B
- Inkling vs LFM3-VL-2B
- Inkling vs Muse Glimmer 30B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-VL-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Muse Glimmer 30B
- Kimi K3.1 Pro vs LFM3-VL-2B
- Kimi K3.1 Pro vs Muse Glimmer 30B
- Kimi K3 vs LFM3-VL-2B
- Kimi K3 vs Muse Glimmer 30B
- Kolibri-1 vs LFM3-VL-2B
- Kolibri-1 vs Muse Glimmer 30B
- Kronos vs LFM3-VL-2B
- Kronos vs Muse Glimmer 30B
- Laguna M.1 vs LFM3-VL-2B
- Laguna M.1 vs Muse Glimmer 30B
- Laguna S 2.1 vs LFM3-VL-2B
- Laguna S 2.1 vs Muse Glimmer 30B
- Laguna XS 2.1 vs LFM3-VL-2B
- Laguna XS 2.1 vs Muse Glimmer 30B
- LBS-27B vs LFM3-VL-2B
- LBS-27B vs Muse Glimmer 30B
- LFM2.5-2.6B vs LFM3-VL-2B
- LFM2.5-2.6B vs Muse Glimmer 30B
- LFM3-1.7B vs LFM3-VL-2B
- LFM3-1.7B vs Muse Glimmer 30B
- LFM3-Audio-2B vs LFM3-VL-2B
- LFM3-Audio-2B vs Muse Glimmer 30B
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs Muse Glimmer 30B
- LFM3-VL-2B vs Ling-3.0-tiny
- LFM3-VL-2B vs Ling-3.1-flash-1019
- LFM3-VL-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-VL-2B vs MiniCPM-o 4.5
- LFM3-VL-2B vs MiniCPM-V 4.7 1B
- LFM3-VL-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-VL-2B vs MiniCPM5-2B
- LFM3-VL-2B vs MiniMax-M2.5
- LFM3-VL-2B vs MiniMax-M2.7
- LFM3-VL-2B vs MiniMax-M3.1-Flash
- LFM3-VL-2B vs Mistral Large 4
- LFM3-VL-2B vs Nanbeige4.3-33B
- LFM3-VL-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-VL-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 4B
- LFM3-VL-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-VL-2B vs Nemotron 3 Super 120B A12B
- LFM3-VL-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-VL-2B vs occamy-1.0
- LFM3-VL-2B vs Olmo 3 7B Think
- LFM3-VL-2B vs Ornith-1.5-122B
- LFM3-VL-2B vs Ornith-1.5-35B-A3B
- LFM3-VL-2B vs Ornith-1.5-397B
- LFM3-VL-2B vs Ornith-1.5-9B
- LFM3-VL-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-VL-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-VL-2B vs Qwen3-4B-Instruct-2507
- LFM3-VL-2B vs Qwen3.5-0.8B
- LFM3-VL-2B vs Qwen3.5-122B-A10B
- LFM3-VL-2B vs Qwen3.5-2B
- LFM3-VL-2B vs Qwen3.5-397B-A17B
- LFM3-VL-2B vs Qwen3.5-4B
- LFM3-VL-2B vs Qwen3.5-9B
- LFM3-VL-2B vs Qwen3.6-27B
- LFM3-VL-2B vs Qwen3.6-35B-A3B
- LFM3-VL-2B vs Qwen3.8-27B
- LFM3-VL-2B vs Qwen3.8-Flash-Next
- LFM3-VL-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-Coder-Next
- LFM3-VL-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-2B-Instruct
- LFM3-VL-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-32B-Instruct
- LFM3-VL-2B vs Qwen3-VL-4B-Instruct
- LFM3-VL-2B vs Qwen3-VL-8B-Instruct
- LFM3-VL-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-VL-2B vs Recursive Flint
- LFM3-VL-2B vs Ripple-65B Preview
- LFM3-VL-2B vs SmolLM3-3B
- LFM3-VL-2B vs Spark-X2.6-4B
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-VL-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-VL-2B vs Baidu Unlimited-OCR-2
- Ling-3.0-tiny vs Muse Glimmer 30B
- Ling-3.1-flash-1019 vs Muse Glimmer 30B
- MiMo-V2.6 Distill Qwen 9B vs Muse Glimmer 30B
- MiniCPM-o 4.5 vs Muse Glimmer 30B
- MiniCPM-V 4.7 1B vs Muse Glimmer 30B
- MiniCPM-V 4.7 35B-A3B vs Muse Glimmer 30B
- MiniCPM5-2B vs Muse Glimmer 30B
- MiniMax-M2.5 vs Muse Glimmer 30B
- MiniMax-M2.7 vs Muse Glimmer 30B
- MiniMax-M3.1-Flash vs Muse Glimmer 30B
- Mistral Large 4 vs Muse Glimmer 30B
- Muse Glimmer 30B vs Nanbeige4.3-33B
- Muse Glimmer 30B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Muse Glimmer 30B vs Nemotron 3.5 Lightning 30B A3B
- Muse Glimmer 30B vs Nemotron 3 Nano 30B A3B
- Muse Glimmer 30B vs Nemotron 3 Nano 4B
- Muse Glimmer 30B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Muse Glimmer 30B vs Nemotron 3 Super 120B A12B
- Muse Glimmer 30B vs Nemotron 3 Ultra 550B A55B
- Muse Glimmer 30B vs occamy-1.0
- Muse Glimmer 30B vs Olmo 3 7B Think
- Muse Glimmer 30B vs Ornith-1.5-122B
- Muse Glimmer 30B vs Ornith-1.5-35B-A3B
- Muse Glimmer 30B vs Ornith-1.5-397B
- Muse Glimmer 30B vs Ornith-1.5-9B
- Muse Glimmer 30B vs Qwen-AgentWorld-35B-A3B
- Muse Glimmer 30B vs Qwen3-30B-A3B-Instruct-2507
- Muse Glimmer 30B vs Qwen3-4B-Instruct-2507
- Muse Glimmer 30B vs Qwen3.5-0.8B
- Muse Glimmer 30B vs Qwen3.5-122B-A10B
- Muse Glimmer 30B vs Qwen3.5-2B
- Muse Glimmer 30B vs Qwen3.5-397B-A17B
- Muse Glimmer 30B vs Qwen3.5-4B
- Muse Glimmer 30B vs Qwen3.5-9B
- Muse Glimmer 30B vs Qwen3.6-27B
- Muse Glimmer 30B vs Qwen3.6-35B-A3B
- Muse Glimmer 30B vs Qwen3.8-27B
- Muse Glimmer 30B vs Qwen3.8-Flash-Next
- Muse Glimmer 30B vs Qwen3-Coder-30B-A3B-Instruct
- Muse Glimmer 30B vs Qwen3-Coder-Next
- Muse Glimmer 30B vs Qwen3-Omni-30B-A3B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-2B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-30B-A3B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-32B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-4B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-8B-Instruct
- Muse Glimmer 30B vs Qwopus3.8-27B-Flash-V2
- Muse Glimmer 30B vs Recursive Flint
- Muse Glimmer 30B vs Ripple-65B Preview
- Muse Glimmer 30B vs SmolLM3-3B
- Muse Glimmer 30B vs Spark-X2.6-4B
- Muse Glimmer 30B vs Swift 1.5 Qwen3.8-27B
- Muse Glimmer 30B vs Swift 1.5 Qwen3.8-Flash-Next
- Muse Glimmer 30B vs ThinkingCap (Qwen3.8 27B)
- Muse Glimmer 30B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/lfm3-vl-2b-vs-muse-glimmer-30b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm3-vl-2b.json·/api/v1/tools/muse-glimmer-30b.json - From a terminal
anchor compare lfm3-vl-2b muse-glimmer-30b(the CLI) - Over MCP
compare_tools {"a": "lfm3-vl-2b", "b": "muse-glimmer-30b"}at/mcp, no key