Muse Glimmer 30B vs Nemotron 3 Nano 30B A3B

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 Nano 30B A3B

A fast hybrid Mamba-Transformer cousin with 3.5B active parameters for reasoning and tool calling over very long inputs, in every major local runtime. A 4-bit build needs about 22 to 23 GB. The main risks are that NVIDIA's documented vLLM path runs repository code, no safety results are published and NVIDIA hasn't answered reports since March.

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 Nano 30B A3B

1. Start it with ollama run nemotron-3-nano:30b (18 GB MLX on a Mac, 24 GB q4_K_M elsewhere)
2. On the reference machine use BF16 with vLLM, after wget https://huggingface.co/nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16/resolve/main/nano_v3_reasoning_parser.py, then vllm serve nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 --max-model-len 262144 --trust-remote-code --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser-plugin nano_v3_reasoning_parser.py --reasoning-parser nano_v3
3. NVFP4 needs an NVIDIA Blackwell GPU, and FP8 isn't documented on gfx1151
4. Without the qwen3_coder tool parser and the nano_v3 reasoning parser, tool calls and reasoning come back as plain text
5. Card sampling is temperature 0.6 and top_p 0.95 for tool calling, temperature 1.0 and top_p 1.0 for reasoning
6. Thinking is on by default, so pass enable_thinking as false in chat_template_kwargs for short tasks
7. Set VLLM_ALLOW_LONG_MAX_MODEL_LEN=1 and raise --max-model-len only when you need more than 262,144 tokens
8. In SGLang the main branch names the reasoning parser nemotron_3, not the card's nano_v3
9. Filter untrusted tool results before they reach the model, as NVIDIA warns prompt injection can lead to code execution
10. Validate JSON output yourself or use the runtime's guided decoding, since none is documented for the model