EXAONE 4.5 33B vs GLM-5.3-Flash

EXAONE 4.5 33B 85

Chat template 20, chat_template.jinja in the repository (5,930 characters). Tool-calling format 25, the card's vLLM command names the parser, hermes with auto tool choice, and its agentic example calls tools from MCP servers through the OpenAI-compatible API, so declaration and return follow that API. Trained tool calling 20, the card reports agentic tool use among its language results and shows an agent run with several tool servers, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, enable_thinking is on by default and the card says to set it false for the non-reasoning mode, with an example of each. Context 10, 262,144 tokens per the card's configuration table and config.json, and the card's serve commands run at that length. 20 + 25 + 20 + 0 + 10 + 10 = 85.

GLM-5.3-Flash 70

A Jinja chat template sits in both repositories, for 20. The tool-calling format is 10, because it is defined only by the template and the glm47 parser is named by vLLM and SGLang rather than by Z.ai. The template takes several calls in one turn, for 20. Structured output is 0, with nothing on the card and only the hosted API documented for JSON. Reasoning control is 10, a per-request budget through reasoning_effort, with the reasoning coming back in a think block, though thinking can't be turned off. Context is 10, 1,048,576 tokens native with no rotary scaling.

EXAONE 4.5 33B 50

Model card 20, Uses (the quickstart's question answering, document and agent examples), limitations, the architecture, the parameters, the context, the languages (in the metadata) and a knowledge cut-off of December 2024 are all on the card. Training data 5, A knowledge cut-off and one line on excluding personal, harmful and biased content, with no sources or sizes. Last change 10, the main repository last changed on 6 July 2026 (dependencies moved to official releases), 127 days before this check, and the FP8 repository on 9 August, 93 days. Responsiveness 0, none of the 5 most recent discussions that aren't pull requests (13 April to 4 May 2026) has a reply from an LGAI-EXAONE member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, EXAONE 4.0 and 4.0.1 stay in their own repositories and 4.5 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the 262,144 tokens, and a July commit moved the dependencies to released versions. 20 + 5 + 10 + 0 + 5 + 10 = 50.

GLM-5.3-Flash 58

The card covers architecture, parameters and languages and misses four of the seven items, for 8. Training data is 5, a 30T-token corpus described with no sources or cut-off. The last change, a chat template speed-up on 15 October in both repositories, is within 30 days on 2 November, for 20; Z.ai's GLM-5 GitHub repository has changed only its docs since. Responsiveness is 10, as zai-org answered 14 of the 38 recent discussions others opened (26 August to 30 October), the last on 28 September, which is some but not most. Version policy is 5 for a first release, and file health is the full 10, with files and card agreeing and no broken-file report waiting as far as the research record shows.

EXAONE 4.5 33B 65

Memory 20, the smallest build at 4 bits is LG's IQ4_XS GGUF, 18.03 GB with the 2.57 GB projector, and 20.60 GB × 1.2 = 24.7 GB, within 32 GB. Without the projector, for text only, it would fit 24 GB. Runtimes 15, Released vLLM 0.33.0 has exaone4_5.py, Transformers 5.22.2 has the exaone4_5 model, and llama.cpp b12242 has the architecture, with LG's own GGUF. Three at 5 each. Builds 15, LG publishes GGUF at five quantised precisions, an AWQ build and an FP8 build. Terms 5, Research and educational use only. Download 10, the Hub API reports gated false for all four repositories on 10 November 2026, so the files download with no account and no click-through, though the licence says downloading is acceptance. Hosted 0, Hugging Face maps no inference provider to it, and the card names no API that serves it. 20 + 15 + 15 + 5 + 10 + 0 = 65.

GLM-5.3-Flash 60

Memory earns nothing, since Z.ai's smallest build is the 328.4 GB FP8 one, about 394 GB with the fifth added, and neither Ollama nor LM Studio has a local build (both list it as cloud only). Four runtimes run it in a released version, llama.cpp, vLLM, SGLang and Transformers, for 20, while Ollama and LM Studio don't. Z.ai publishes one quantised build, FP8, for 10. The MIT licence with nothing added gives the full 15, the files download with no account or gate for 10, and Z.ai's own API plus six providers on Hugging Face serve it, for 5.

EXAONE 4.5 33B 50

File safety 25, safetensors and GGUF only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the LGAI-EXAONE organisation (LG AI Research on the Hub), which the card's GitHub repository shares a name with and the licence in the repository is LG's (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions: the limitation section lists inappropriate, biased, incorrect and outdated answers and tells users not to try to induce harmful output. Licence risk 5, 15 less 5 for field-of-use limits beyond the law (no commercial use, no building competing models) and 5 for terms the licensor can change or revoke (LG may amend the agreement at any time, and the licence is revocable). Security programme 0, no way to report a flaw on the card beyond a support contact, and www.lgresearch.ai has no security.txt. 25 + 15 + 0 + 5 + 5 + 0 = 50.

GLM-5.3-Flash 55

File safety is full, with safetensors only, no Python and no remote code needed in Transformers 5.16.1 or later. Provenance is full, files in the zai-org organisation Z.ai links from GitHub with a SHA-256 for every shard. Safety evaluation and agent guidance are 0, as nothing is published on either. Licence risk is the full 15, since MIT adds no policy, threshold or changeable terms. The security programme is 0, with no security.txt on z.ai or docs.z.ai, no SECURITY.md on GitHub and no advisories found.