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

GLM-5.3 vs Qwen3.5-397B-A17B

GLM-5.3 and Qwen3.5-397B-A17B score within a point of each other on agent readiness, 64.6 (B) and 64.6 (B). Qwen3.5-397B-A17B leads on reach and risk. 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

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 72
  • Documentation and upkeep, 58 against 39

Watch for

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

Qwen3.5-397B-A17B B

Best for Agents with access to an 8-GPU server, or calling a hosted endpoint, that want the strongest open Qwen3.5 with vision and a plain licence.

Ahead on

  • Reach, 70 against 55
  • Risk, 55 against 50

Watch for

No build fits a 256 GB machine, and Ollama has no local build

Score by category

CategoryWeight this runGLM-5.3Qwen3.5-397B-A17BEdge
Capability35%358072GLM-5.3 +8
Reach25%255570Qwen3.5-397B-A17B +15
Risk20%205055Qwen3.5-397B-A17B +5
Agent interface10%107070even
Documentation and upkeep10%105839GLM-5.3 +19
Negative events≤1500
TotalB 64.6/100B 64.6/100

Facts side by side

FactGLM-5.3Qwen3.5-397B-A17B
KindOpen-weight modelOpen-weight model
VendorZ.ai (Zhipu AI)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceGLM-5.3 License (MIT-style, with a security review for the largest model-as-a-service operators)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-142026-02-16
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 reviews2.8/5 (4)2.8/5 (4)

Verdicts

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.

Qwen3.5-397B-A17B

Alibaba's biggest open Qwen3.5, a cousin for hard coding, agent and vision work. Even at 4 bits it needs about 270 GB, so most agents will call it through Alibaba's Model Studio or one of the many providers that host it. The main risk is silence, with no safety results, no agent guidance and template reports without a reply.

Before you call either

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

Qwen3.5-397B-A17B

  1. The card's server command is vllm serve Qwen/Qwen3.5-397B-A17B --port 8000 --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, and the FP8 build halves the memory
  2. It doesn't fit our 128 GB reference machine at any precision, so call a hosted endpoint instead (Model Studio's Qwen3.5-Plus, or a provider serving Qwen/Qwen3.5-397B-A17B)
  3. On Model Studio pass "enable_thinking": false directly, while vLLM and SGLang take "chat_template_kwargs": {"enable_thinking": false}
  4. Sampling per the card is temperature 0.6, top_p 0.95 and top_k 20 when thinking, and temperature 0.7, top_p 0.8, top_k 20 and presence_penalty 1.5 without
  5. For multi-token prediction in vLLM add --speculative-config '{"method":"qwen3_next_mtp","num_speculative_tokens":2}'
  6. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  7. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, GLM-5.3 or Qwen3.5-397B-A17B?

GLM-5.3 and Qwen3.5-397B-A17B score within a point of each other on agent readiness, 64.6 (B) and 64.6 (B). Qwen3.5-397B-A17B leads on reach and risk.

Other comparisons with GLM-5.3 or Qwen3.5-397B-A17B

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.