MiniCPM5-2B vs Ornith-1.5-35B-A3B

MiniCPM5-2B

A tiny dense cousin for local tool calling and long context, with published training data and an active publisher. OpenBMB's own 4-bit builds need about 2 GB, so it runs on a laptop or phone in vLLM, SGLang, llama.cpp, Ollama or Transformers. The main risks are always-on thinking, no safety results and use conditions beyond Apache 2.0.

Ornith-1.5-35B-A3B

A mid-size coding and terminal-agent cousin with about 3B active parameters, XML tool calls that vLLM and SGLang parse and 262,144 tokens of context. It runs in about 24 GB from Ornith's MLX 4-bit build or 32 GB from its GGUF. The main risk is an absent publisher, with no licence file, safety results or replies to 35 reports.

MiniCPM5-2B

1. Smallest start is ollama run openbmb/minicpm5-2b (1.6 GB, q4_k_m)
2. On vLLM 0.29.0 or later run vllm serve openbmb/MiniCPM5-2B --max-model-len 131072 --enable-auto-tool-choice --tool-call-parser minicpm5, or tool calls come back as XML text
3. On SGLang 0.5.16 or later add --tool-call-parser minicpm5 --reasoning-parser qwen3; SGLang is OpenBMB's recommended backend for tool calls
4. Tool calls are XML, <function name=...><param name=...>, not Hermes JSON
5. Sample with temperature 1.0, top_p 0.95 and min_p 0.0; llama.cpp's default min_p 0.05 can loop, and repetition_penalty 1.05 helps if it does
6. Expect a <think> block before every answer and leave room in max_tokens; enable_thinking false is accepted by the template but OpenBMB doesn't support it for the 2B
7. Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented
8. Use the main repository's template; the GGUF, MLX and GPTQ copies predate the 29 September fix

Ornith-1.5-35B-A3B

1. Start it with ollama run ornith-1.5:35b, or llama-server -hf ornith-ai/Ornith-1.5-35B-A3B-GGUF --port 8000 -c 262144 as the card gives it
2. In vLLM pass --enable-auto-tool-choice --tool-call-parser qwen3_xml --reasoning-parser qwen3, and in SGLang --tool-call-parser qwen3_coder --reasoning-parser qwen3, so tool calls and reasoning come back parsed
3. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
4. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
5. Use temperature 0.6, top_p 0.95, top_k 20 for general tasks and temperature 1.0 to reproduce the card's benchmarks
6. Pin a revision when you download, since Ornith has replaced files in place, and add mmproj-Ornith-1.5-35B-BF16.gguf (0.9 GB) for image input in llama.cpp
7. Validate JSON output yourself, since structured output isn't documented