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.
Alibaba · Q4_K_M · 17.9 GB · up to 64K context · on RTX 4090
- 37.6 t/s
- A
Also worth a look
Q4_K_M · 21.7 GB · 32.1 t/s · 32K ctx
Q4_K_M · 17.9 GB · 37.6 t/s · 64K ctx
Also worth a look
Q4_K_M · 21.7 GB · 32.1 t/s · 32K 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
8 GB · RTX 5060
Qwen3.5 9B45.8 t/s · 32K ctx
Q4_K_M · 6.6 GB
Runner-up: Gemma 4 E4B IT
12 GB · RTX 5070
Qwen3.5 9B68.7 t/s · 128K ctx
Q4_K_M · 6.6 GB
Runner-up: GPT OSS 20B
16 GB · RTX 5080
Qwen3.8 27B42.6 t/s · 32K ctx
Q4_0 · 15.1 GB
Runner-up: Gemma 4 26B A4B IT
24 GB · RTX 4090
Qwen3.8 27B37.6 t/s · 64K ctx
Q4_K_M · 17.9 GB
Runner-up: Gemma 4 31B IT
32 GB · RTX 5090
Qwen3.8 27B66.9 t/s · 256K ctx
Q4_K_M · 17.9 GB
Runner-up: Gemma 4 31B IT
48 GB+ · no limit · about 5× H200 SXM 141 GB
MiMo V2.6 Pro RL1M ctx
Q4_K_M · needs 614 GB
Runner-up: GLM 5.3
Tool-use models that run on 24 GB204
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.
204 models · 165 run great · 14 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 4090
| Model | Quant | VRAM | Speed | Context | Score | Fit |
|---|---|---|---|---|---|---|
Hy MT2 30B A3BTranslationFunctions | Q4_K_M | 19.1 GB | 170.3 t/s | 262K | S98, Runs great | |
Granite Vision 4.1 4BVisionFunctions | Q4_K_M | 4.0 GB | 228.3 t/s | 131K | S100, Runs great | |
MiniCPM V 4.6VisionFunctions | Q4_K_M | 1.5 GB | 579.8 t/s | 262K | S100, Runs great | |
MiniCPM V 4.6 ThinkingVisionFunctions | Q4_K_M | 1.5 GB | 579.8 t/s | 262K | S100, Runs great | |
JiRackDeltaNet 27BChatFunctions | Q4_K_M | 17.6 GB | 38.2 t/s | 262K | A74, Runs well | |
JiRackUltra 1BChatFunctions | Q4_K_M | 1.8 GB | 461.4 t/s | 131K | S100, Runs great | |
Ornith 1.0 9BChatFunctions | Q4_K_M | 6.5 GB | 105.5 t/s | 262K | S92, Runs great | |
DeepSeek R1 0528 Qwen3 8BChatReasoningFunctions | Q4_K_M | 7.6 GB | 118.7 t/s | 131K | S95, Runs great | |
JiRackUltra 14BChatFunctions | Q4_K_M | 12.4 GB | 68.5 t/s | 131K | S85, Runs great | |
Llm Jp 4.1 32B A3b ThinkingChatFunctions | Q4_K_M | 20.1 GB | 187.6 t/s | 66K | S94, Runs great | |
NVIDIA Nemotron Labs Dory1.0 4B BF16ChatFunctions | Q4_K_M | 5.7 GB | 214.1 t/s | 262K | S100, Runs great | |
LFM2.5 VL 450MVisionFunctions | Q4_K_M | 0.8 GB | 1023.8 t/s | 128K | S100, Runs great | |
ZDTaichu5.0 9BVisionFunctions | Q4_K_M | 9.2 GB | 101.4 t/s | — | S92, Runs great | |
ChandraVisionFunctions | Q4_K_M | 8.0 GB | 111.8 t/s | 262K | S94, Runs great | |
ALoDLM 8BChatCodeFunctions | Q4_K_M | 7.6 GB | 118.7 t/s | 41K | S95, Runs great |
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.