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

Granite 4.2 30B vs MiniCPM5-2B

Granite 4.2 30B scores 61 (C) on agent readiness against MiniCPM5-2B's 59.7 (C), and leads in 1 of 4 scored categories. MiniCPM5-2B 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 4969 open weights comparisons

Which one, for what

Granite 4.2 30B C

Best for Agents that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 24 GB card

Ahead on

  • Agent interface, 85 against 75

Watch for

No safety results published for it

MiniCPM5-2B C

Best for On-device and laptop agents that want a 2 GB tool-calling helper with long context and open training data

Ahead on

  • Documentation and upkeep, 92 against 87

Watch for

OpenBMB documents only a Think mode for the 2B, so every answer starts with reasoning

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.

Agent interface Granite 4.2 30B +10

Granite 4.2 30B 85

Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

MiniCPM5-2B 75

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card and OpenBMB's cookbooks document the XML call format, the tools request and the minicpm5 parser in SGLang and vLLM. Trained tool calling 20, agent SFT on 500K samples and a template that renders several calls in one turn. Structured output 0, nothing documents asking for JSON. Reasoning control 0, a judgement call, because OpenBMB's own cookbooks call Think the only supported mode for the 2B even though the template accepts enable_thinking false. Context 10, 131,072 tokens native with no rope scaling.

Documentation and upkeep MiniCPM5-2B +5

Granite 4.2 30B 87

Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (30B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 30B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 15, the last commit to the repository was on 4 September 2026, 67 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (28 August to 3 November 2026), 3 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 30B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 15 + 20 + 5 + 10 = 87.

MiniCPM5-2B 92

Model card 17, everything but a knowledge cut-off. Training data 20, all eight training datasets are published on Hugging Face and named per stage with sizes. Last change 15, a template fix on 29 September 2026, 36 days ago, with nothing newer in OpenBMB's MiniCPM5 repositories on Hugging Face (builds last changed 12 September) or its GitHub repository (21 September). Responsiveness 20, OpenBMB members answered 16 of the 23 questions in the discussions, the newest reply on 29 September. Version policy 10, earlier models and checkpoints sit in their own repositories and the GitHub changelog dates each release. File health 10, config, tokenizer, template and card agree and no broken-file report waited on 21 October, though OpenBMB's GGUF, MLX and GPTQ repositories still carry the template from before the 29 September fix.

Score by category

CategoryWeight this runGranite 4.2 30BMiniCPM5-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259090even
Risk20%205555even
Agent interface10%108575Granite 4.2 30B +10
Documentation and upkeep10%108792MiniCPM5-2B +5
Negative events≤1500
TotalC 61/100C 59.7/100

Facts side by side

FactGranite 4.2 30BMiniCPM5-2B
KindOpen-weight modelOpen-weight model
VendorIBMOpenBMB
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-09-042026-09-29
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/5 (4)

How the scores have moved

Granite 4.2 30B

No score change since it was listed.

MiniCPM5-2B

Verdicts

Granite 4.2 30B

IBM's largest reasoning cousin, with the same strengths as the 3B. It runs in every runtime we count from IBM's own builds on a 24 GB card, is signed, plain Apache 2.0, and comes with a disclosure of its training data. No safety results are published and structured output isn't documented.

MiniCPM5-2B

A 2B dense model for local tool calling and long context, with published training data. OpenBMB's own 4-bit builds are under 1.6 GB, and the model loads in vLLM, SGLang, llama.cpp, Ollama and Transformers. The main risks are always-on thinking, no safety results and use conditions beyond Apache 2.0.

Before you call either

Granite 4.2 30B

  1. Start it with ollama run granite4.2:30b, or llama-server -hf ibm-granite/granite-4.2-30b-GGUF:Q4_K_M --jinja
  2. With vLLM 0.32.0 or later leave out --reasoning-parser-plugin, since the parser is built in, and use --tool-call-parser qwen3_coder
  3. Thinking is on by default. Pass enable_thinking false to turn it off or low_effort true for short reasoning
  4. The context is 131,072 tokens. The card's 512K extension isn't documented
  5. Validate JSON output yourself, since structured output isn't documented
  6. IBM recommends Granite Guardian beside it to flag risky inputs and outputs

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

Questions

Which is better for AI agents, Granite 4.2 30B or MiniCPM5-2B?

Granite 4.2 30B scores 61 (C) on agent readiness against MiniCPM5-2B's 59.7 (C), and leads in 1 of 4 scored categories. MiniCPM5-2B leads on documentation and upkeep.

Other comparisons with Granite 4.2 30B or MiniCPM5-2B

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.