Muse Glimmer 30B vs Nemotron 3 Nano 4B

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 4B

A tiny reasoning cousin with trained tool calls, a thinking switch and 262,144 tokens of context, running in about 4 GB from NVIDIA's own GGUF on almost any machine. The main risks are serving commands that run repository code, no published safety results, a tool format left to the template, and files untouched and questions unanswered 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 4B

1. Quickest start is ollama run nemotron-3-nano:4b, a 2.8 GB build
2. With llama.cpp use llama-server -hf nvidia/NVIDIA-Nemotron-3-Nano-4B-GGUF --jinja, NVIDIA's own Q4_K_M file
3. With vLLM, download nano_v3_reasoning_parser.py from the repository first and serve with --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser-plugin nano_v3_reasoning_parser.py --reasoning-parser nano_v3
4. The card's Transformers snippet names nvidia/NVIDIA-Nemotron-3-Nano-4B, use nvidia/NVIDIA-Nemotron-3-Nano-4B-BF16 instead
5. Thinking is on by default. Pass enable_thinking=False to the chat template for short tasks
6. Use temperature 1.0 and top_p 0.95 for reasoning and temperature 0.6 with top_p 0.95 for tool calling, as the card says
7. It's tuned for English only, and validate JSON yourself, since structured output isn't documented