TinyToolRouter 0.6B needs about 1.8 GB of memory at Q4_K_M (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 3 quants, from 0.4 GB (Q4_K_M) to 1.2 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
TinyToolRouter 0.6B – a lightweight tool‑routing LLM
TinyToolRouter 0.6B is a 0.6‑billion‑parameter model fine‑tuned from Qwen3‑0.6B to select tools from a supplied schema. It outputs a single structured JSON tool call or a no_tool response. The model runs efficiently on CPU‑first setups.
Good at
- Tool selection from dynamic schemas
- Structured JSON output
- Explicit abstention when no tool applies
Limits
- No vision support
- Requires 8,192‑token context for full operation
- License is apache‑2.0
Best for
- Chatbot tool integration
- Automated workflow orchestration
- API‑based tool routing
Who it’s for. Developers building lightweight, CPU‑first agents that need reliable tool selection. The model is ideal for edge deployments where memory and compute are limited.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.4 GB | 1.8 GB | Fits | Get file → | |
| Q8_0 | 0.6 GB | 2.1 GB | Fits | Get file → | |
| F16 | 1.2 GB | 2.6 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_M (0.4 GB file, ~1.8 GB memory at 8k context). For 12 GB VRAM, Q8_0 (0.64 GB file, ~2.1 GB memory). For higher precision and 16 GB VRAM, F16 (1.2 GB file, ~2.6 GB memory).
What GPU do you need for TinyToolRouter 0.6B?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is F16 (1.2 GB file, about 2.6 GB in use).
Which TinyToolRouter 0.6B quant should you choose?
Q4_K_M is the usual starting point for TinyToolRouter 0.6B: it balances file size and quality well. Here it is a 0.4 GB file.
The Q8_0 file is 0.6 GB, about 1.6 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about TinyToolRouter 0.6B
How much VRAM does TinyToolRouter 0.6B need?
About 1.8 GB at Q4_K_M with an 8K context window. That is the 0.4 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run TinyToolRouter 0.6B on an 8 GB GPU?
Yes, with F16: the 1.2 GB file needs about 2.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of TinyToolRouter 0.6B GGUF?
It depends on the quant: Q4_K_M is 0.4 GB, Q8_0 is 0.6 GB, F16 is 1.2 GB.
What context length does TinyToolRouter 0.6B support?
The GGUF header lists a trained context length of 40,960 tokens (40K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.
Where can I download TinyToolRouter 0.6B GGUF?
The files are on Hugging Face in the Robokid1134/TinyToolRouter-0.6B repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does TinyToolRouter 0.6B use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run TinyToolRouter 0.6B on 8 GB VRAM?
Yes, the Q4_K_M quantization requires about 1.8 GB of VRAM at 8k context, fitting comfortably in 8 GB.
Does the model support vision or image input?
No, TinyToolRouter 0.6B is a text‑only model with no vision capabilities.
What license applies to this model?
The model is released under the apache‑2.0 license.