Muse Glimmer 30B vs Nemotron 3 Super 120B A12B

Muse Glimmer 30B

A dense 30B multimodal cousin for local agent and coding work with images, documented tool calls and adjustable reasoning. Meta's 17 GB GGUF fits a 24 GB card and runs in llama.cpp, Ollama, vLLM, SGLang and Transformers. The main risks are one tool call per turn, no documented JSON output and a usage policy that adds limits to Apache 2.0.

Nemotron 3 Super 120B A12B

A long-context agent cousin with trained parallel tool calls, a reasoning switch and a full account of its training data, under a free commercial licence. It needs about 100 GB of GPU memory, a 128 GB unified machine or Blackwell hardware for NVIDIA's NVFP4. The main risks are serving commands that run repository code and no published safety results.

Muse Glimmer 30B

1. Start it with llama serve -hf meta-models/Muse-Glimmer-30B-GGUF --hf-file Muse-Glimmer-30B-KQuant-17GB-Q4_K_M.gguf -ngl 99 -c 131072 --host 127.0.0.1 --port 8080 --chat-template-kwargs '{"reasoning_strength":"high"}' on llama.cpp b10353 or later, or ollama run muse-glimmer on Ollama 0.32.7 or later
2. In vLLM pass --tool-call-parser muse_glimmer --reasoning-parser muse_glimmer, in SGLang muse for both, in ExecuTorch --tool-parser atem. Without them tool calls come back as plain text
3. Set reasoning per request with chat_template_kwargs.reasoning_strength (low, medium, high or xhigh). llama.cpp and ExecuTorch don't read reasoning_effort, and ExecuTorch rejects it with a 400
4. Expect one tool call per turn and return each result before the next. ExecuTorch's server rejects tool_choice="required"
5. Keep temperature 1.0, top_p 0.95 and top_k 64, don't run greedy, and never stop on <|eom|>
6. Leave max_tokens room for reasoning, since in llama.cpp a request cut off mid-thought returns empty content with finish_reason length
7. For images add Meta's 1.4 GB mmproj GGUF, which takes the build to about 22 GB with the runtime's fifth

Nemotron 3 Super 120B A12B

1. On the reference machine start it with ollama run nemotron-3-super, the 87 GB q4_K_M build, the only one that fits (about 104 GB with the margin)
2. Raise the Strix Halo GPU memory limit first with amd-ttm --set 100, since the default of about 62.8 GiB is far below what it needs
3. With vLLM serve it with --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder (SGLang uses --reasoning-parser nemotron_3)
4. Use temperature=1.0 and top_p=0.95 for every task, as the card says
5. Thinking is on by default. Pass enable_thinking: false or low_effort: true in chat_template_kwargs for short tasks
6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, so a cut-off reasoning trace still returns content
7. Raise context past 262,144 only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576)