LFM2.5-2.6B vs Muse Glimmer 30B

LFM2.5-2.6B

A small, fast cousin for tool calls, extraction and long-context steps on a laptop or phone. Liquid's own 4-bit build is 1.6 GB, and every common runtime runs it. It always thinks, isn't meant for coding or knowledge-heavy work, and organisations over $10M of revenue need another licence. There are no safety results or security contact.

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.

LFM2.5-2.6B

1. Quickest start is ollama run LiquidAI/lfm2.5-2.6b, 1.7 GB, or llama-cli -hf LiquidAI/LFM2.5-2.6B-GGUF
2. With vLLM or SGLang pass --tool-call-parser lfm2; for vLLM add --reasoning-parser qwen3 so the thinking comes back separately
3. Sample at temperature 0.1, top_k 50 and repetition_penalty 1.1, as the card and generation_config.json set
4. Put tools in the system prompt as List of tools: [...] JSON, or pass tools to apply_chat_template; calls come back as a Python list of function calls, and the system prompt can ask for JSON calls instead
5. Leave max_tokens unset or generous, since a low cap cuts the reasoning off mid-thought
6. Earlier thinking is dropped from the prompt unless preserve_thinking is true
7. Liquid's 328M LFM2.5-2.6B-DSpark drafter speeds decoding about 2.6 times in SGLang and on Apple silicon, per Liquid
8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Muse Glimmer 30B

1. 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, or ollama run muse-glimmer on Ollama 0.32.7 or later
2. In vLLM pass --tool-call-parser muse_glimmer --reasoning-parser muse_glimmer, in SGLang muse for both, in ExecuTorch --tool-parser atem. Without them tool calls come back as plain text
3. Set reasoning per request with chat_template_kwargs.reasoning_strength (low, medium, high or xhigh). llama.cpp and ExecuTorch don't read reasoning_effort, and ExecuTorch rejects it with a 400
4. Expect one tool call per turn and return each result before the next. ExecuTorch's server rejects tool_choice="required"
5. Keep temperature 1.0, top_p 0.95 and top_k 64, don't run greedy, and never stop on <|eom|>
6. Leave max_tokens room for reasoning, since in llama.cpp a request cut off mid-thought returns empty content with finish_reason length
7. For images add Meta's 1.4 GB mmproj GGUF, which takes the build to about 22 GB with the runtime's fifth