Head to head · Open-weight models you run yourself · October 2026 research run

Muse Glimmer 30B vs Spark-X2.6-4B

Muse Glimmer 30B scores 70 (BB) on agent readiness against Spark-X2.6-4B's 61 (C), and leads in every scored category. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

Muse Glimmer 30B BB

Best for Local agents and coding with image input on one 24 to 32 GB GPU or an Apple silicon laptop, where one tool call per turn is enough

Ahead on

  • Reach, 90 against 85
  • Risk, 80 against 50
  • Agent interface, 75 against 70
  • Documentation and upkeep, 65 against 41

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.8 against 3.0 out of 5

Watch for

One tool call per turn and no parallel calls

Spark-X2.6-4B C

Best for Agents that want a tiny local model for tool loops and long documents on a laptop, CPU or small GPU.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No safety results and no agent or prompt-injection guidance

Score by category

CategoryWeight this runMuse Glimmer 30BSpark-X2.6-4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259085Muse Glimmer 30B +5
Risk20%208050Muse Glimmer 30B +30
Agent interface10%107570Muse Glimmer 30B +5
Documentation and upkeep10%106541Muse Glimmer 30B +24
Negative events≤1500
TotalBB 70/100C 61/100

Facts side by side

FactMuse Glimmer 30BSpark-X2.6-4B
KindOpen-weight modelOpen-weight model
VendorMetaSparkLLM (XHToken)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-10-202026-10-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.8/5 (4)3/5 (4)

Verdicts

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.

Spark-X2.6-4B

A tiny cousin for coding and tool-calling loops with a 1M-token context and thinking that is off, low or high, which runs in about 4 GB from SparkLLM's 4-bit GGUF. Use llama.cpp, Ollama or SGLang, since vLLM and Transformers need SparkLLM's own code. The risks are no safety work or agent guidance and a thin, two-day-old card.

Before you call either

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

Spark-X2.6-4B

  1. Quickest start is llama-server -hf XHToken/Spark-X2.6-4B-GGUF:Q4_K_M --jinja, which needs llama.cpp b10828 or later, or ollama run SparkLLM/Spark-X2.6-4B (8.2 GB, Ollama 0.34.1 or later)
  2. For parsed tool calls serve it with SGLang 0.5.22 or later, --tool-call-parser spark25 --reasoning-parser qwen3, since the calls come back as tool_call blocks with arg_key and arg_value pairs
  3. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false to turn it off, or reasoning_effort low for short thinking; the template raises an error on any effort other than high or low
  4. SparkLLM's recommended sampling is temperature 1.0, top_p 0.95 and top_k -1
  5. The template always opens with its own default system line, with the effort instruction, and puts your system message after the tool list
  6. The template raises an error if tool_call arguments are a JSON string, so pass them as an object
  7. Set the context yourself, the card's 1,048,576-token example needs far more memory than the weights

Questions

Which is better for AI agents, Muse Glimmer 30B or Spark-X2.6-4B?

Muse Glimmer 30B scores 70 (BB) on agent readiness against Spark-X2.6-4B's 61 (C), and leads in every scored category.

Other comparisons with Muse Glimmer 30B or Spark-X2.6-4B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.