llmrun

Best local LLMs for tool use

Run open models capable of function calling, designed for agents and apps that use tools and APIs. We rank them using the llmrun Composite Score, offering the top choice for every memory capacity.

Best for tool use on

Qwen3.5 9B

Alibaba · Q4_K_M · 6.6 GB · up to 32K context · on RTX 5060

45.8 t/s
A

All 129 tool-use models for 8 GB ↓

Also worth a look

Gemma 4 E4B IT

Q4_K_M · 5.6 GB · 54.7 t/s · 64K ctx

Best tool-use model by memory

Highest llmrun Composite Score that fits each size with at least 32K context and 15 t/s, at a Q3 or better quant. Speed is decode tokens per second on that size's reference GPU. The last row has no memory limit: the best model whatever it needs, on the GPU plan shown. Full ranking

Tool-use models that run on 8 GB129

Ranked by Composite Score, models without one after. Best quant that fits with a 16K context; speed is decode tokens per second on the reference GPU.

129 models · 73 run great · 28 run well

Score: llmrun Score, 100 = average model. Fit: how well it runs on this hardware, S best to F won't fit. Ordered by Score, recency and Fit. How ranking works

Showing compatibility for NVIDIA GeForce RTX 5060

LLM models compatible with NVIDIA GeForce RTX 5060 — ranked by Score, recency and Fit
ModelVRAMScoreFit
K2 Horizon 7B
< 32K context fits
Q4_K_S·51.4 t/s
7.8 GBB54, Decent
Chandra
< 32K context fits
Q4_K_M·49.7 t/s
8.0 GBC44, Usable
Granite 4.0 350M
Q4_K_M·510.9 t/s
1.0 GBS100, Runs great
Olmo 3 7B Instruct
< 32K context fits
IQ4_XS·54.9 t/s
8.0 GBC44, Usable
LFM2.5 350M
Q4_K_M·502.1 t/s
0.8 GBS100, Runs great
Dream V0 Instruct 7B
Q4_K_M·58.4 t/s
5.8 GBA83, Runs well
< 32K context fits
Q4_K_M·323.6 t/s
1.3 GBS100, Runs great
Q4_K_M·100.4 t/s
2.9 GBS91, Runs great
Granite Switch 4.1 8B
< 32K context fits
Q3_K_L·56.5 t/s
7.6 GBB60, Decent
Granite 4.0 H Tiny
Q4_K_M·179.9 t/s
5.8 GBS99, Runs great
Llama 3.2 1B Instruct
Q4_K_M·355.1 t/s
2.3 GBS100, Runs great
Qwen2.5 3B Instruct
Q4_K_M·130.6 t/s
2.8 GBS95, Runs great
Qwen2.5 1.5B Instruct
Q4_K_M·227.5 t/s
1.7 GBS100, Runs great
Q4_K_M·58.4 t/s
5.8 GBA83, Runs well
Qwen3 VL 8B Instruct
< 32K context fits
Q4_K_M·49.7 t/s
8.0 GBC44, Usable

How much memory do you need for a tool-use model?

From 8 to 12 GB the best tool-use model is Qwen3.5 9B (score 99). From 16 to 32 GB it is Qwen3.8 27B (score 122). With no memory limit, the best is MiMo V2.6 Pro RL (score 133). Since agents pass lengthy prompts packed with tool definitions and outcomes, both context window size and processing speed matter. Choose a model that retains a generous amount of context within its memory.

Frequently Asked Questions

What is the best local LLM for tool use?

On 24 GB, Qwen3.8 27B is the top pick with a score of 122, running at about 38 t/s on RTX 4090. It fits up to 64K tokens of context there. On 8 GB, the best fit is Qwen3.5 9B. With no memory limit, the best is MiMo V2.6 Pro RL. Open a model to see which GPUs and Macs run it.

Can I run a tool-use model on a laptop or an 8 GB GPU?

Yes. On 8 GB the best pick is Qwen3.5 9B (Q4_K_M, 6.6 GB), which runs at about 46 t/s on RTX 5060. Laptops with 8 to 16 GB of memory can run smaller models in the same way.

What is tool calling?

Instead of plain text, the model outputs a structured call like a function name plus its arguments. Your code executes that function, sends back the result, and lets the model continue from there.

Which runtime supports tool calling for local models?

Ollama, LM Studio, llama.cpp, and vLLM all offer an OpenAI-compatible tools interface for models built to use it. Remember that the model's chat template needs to support these tools.