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

Gemma 4 31B IT vs GLM-5.3

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against GLM-5.3's 64.6 (B), and leads in 4 of 5 scored categories. GLM-5.3 leads on capability. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

Gemma 4 31B IT BB

Best for An agent with a 24 GB GPU or more that wants a dense multimodal cousin with tool calling under a plain licence

Ahead on

  • Reach, 95 against 55
  • Risk, 70 against 50
  • Agent interface, 85 against 70
  • Documentation and upkeep, 65 against 58

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.8 against 2.8 out of 5

Watch for

No safety evaluation results published

GLM-5.3 B

Best for Teams with an 8-GPU server who want an open coding and long-horizon agent model with a 1M-token context, or agents that call it through Z.ai or a hosted provider

Ahead on

  • Capability, 80 against 61

Watch for

Z.ai's smallest build is 755.6 GB in FP8, with no local Ollama or LM Studio build

Score by category

CategoryWeight this runGemma 4 31B ITGLM-5.3Edge
Capability35%356180GLM-5.3 +19
Reach25%259555Gemma 4 31B IT +40
Risk20%207050Gemma 4 31B IT +20
Agent interface10%108570Gemma 4 31B IT +15
Documentation and upkeep10%106558Gemma 4 31B IT +7
Negative events≤1500
TotalBB 74.1/100B 64.6/100

Facts side by side

FactGemma 4 31B ITGLM-5.3
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindZ.ai (Zhipu AI)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0GLM-5.3 License (MIT-style, with a security review for the largest model-as-a-service operators)
Read-only variant documentednono
llms.txtyesno
Last release2026-07-202026-10-14
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.8/5 (4)2.8/5 (4)

Verdicts

Gemma 4 31B IT

A dense multimodal cousin with documented tool calling, optional thinking and a 256K context, for general agent work and image reading on one 24 GB GPU through Google's 4-bit build. It runs in every major runtime under plain Apache 2.0. The main risk is that Google publishes no safety results and has gone quiet on the repository since July.

GLM-5.3

A large coding and long-horizon agent model with a 1M-token context, several tool calls per turn and three reasoning budgets. Z.ai's smallest build is 756 GB in FP8, so it needs an 8-GPU server, Z.ai's API or a provider. The main risks are no published safety work, no way to report a flaw, and thinking that can't be turned off.

Before you call either

Gemma 4 31B IT

  1. On the reference machine run llama-server -hf google/gemma-4-31B-it-qat-q4_0-gguf --hf-file gemma-4-31B_q4_0-it.gguf --jinja -c 32768, adding gemma-4-31B-it-mmproj.gguf for images
  2. Or ollama run gemma4:31b for the 20 GB Q4_K_M build
  3. In vLLM serve with --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4, as vLLM's recipe does
  4. Thinking is off by default, so pass enable_thinking: true in chat_template_kwargs to turn it on, and expect the reasoning in the thought channel block
  5. Drop earlier thoughts from the history except on tool-call turns, as the card asks
  6. Use the card's sampling, temperature 1.0, top_p 0.95, top_k 64
  7. Validate function names and arguments before running a call, and check JSON output yourself or use the runtime's guided decoding
  8. The w4a16 build relies on Marlin INT4 kernels that vLLM marks unsupported on AMD, so use the GGUF on the reference machine

GLM-5.3

  1. Start it with vllm serve zai-org/GLM-5.3 --kv-cache-dtype fp8 --tensor-parallel-size 8 --speculative-config.method mtp --speculative-config.num_speculative_tokens 5 --tool-call-parser glm47 --reasoning-parser glm47 --enable-auto-tool-choice --served-model-name glm-5.3 (vLLM 0.28.0 or later, 8xH200 or 8xH20 per vLLM's recipe)
  2. Use the glm47 tool-call and reasoning parsers in vLLM or SGLang; SGLang's cookbook says glm45 leaves the calls as plain text
  3. Pass chat_template_kwargs: {"reasoning_effort": "low"} for short tasks; anything other than low or high falls back to max
  4. Pass clear_thinking: true in chat use, since the template keeps earlier reasoning by default
  5. Don't send enable_thinking: false; the template ignores it and always opens a think block
  6. Validate JSON output yourself, since structured output is documented only for Z.ai's hosted API
  7. No Z.ai build fits a 128 GB machine; the full 1M context needs 8xB200 per vLLM's recipe

Questions

Which is better for AI agents, Gemma 4 31B IT or GLM-5.3?

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against GLM-5.3's 64.6 (B), and leads in 4 of 5 scored categories. GLM-5.3 leads on capability.

Other comparisons with Gemma 4 31B IT or GLM-5.3

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.