Muse Glimmer 30B vs Qwen3-30B-A3B-Instruct-2507

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.

Qwen3-30B-A3B-Instruct-2507

A quick general-purpose cousin, with 3.3B of 30.5B parameters active per token, for instruction following, tool calling and long documents without a thinking step. It needs about 21 to 23 GB at 4 bits, and several providers host it. The main risk is neglect, with no file changes in over a year, no answers from Alibaba and no 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

Qwen3-30B-A3B-Instruct-2507

1. Quickest start is ollama run qwen3:30b-instruct, 19 GB. Plain qwen3:30b and qwen3:30b-a3b are the Thinking-2507 edition, not this one
2. On our reference machine use BF16 with vllm serve Qwen/Qwen3-30B-A3B-Instruct-2507 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser hermes, 61 GB of weights fits the GPU share
3. Use the hermes parser in vLLM or qwen25 in SGLang, the template emits JSON inside tool_call tags
4. Don't pass enable_thinking, this edition never thinks and the card says the flag isn't needed
5. Sampling per the card is temperature 0.7, top_p 0.8, top_k 20 and min_p 0, with presence_penalty up to 2 against repetition
6. Leave config.json as it is unless you need more than 262,144 tokens, the 1M mode swaps in config_1m.json and runs one sequence at a time
7. Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented