OC

OculusMind ToolCall 8B v2

OculusmindGGUF by mradermacherUpdated 2026-10-10
Download on Hugging Face
Parameters8.49B
Context256K
Layers34
Architecturemistral3
Smallest quant3.4 GB
Quick answer

OculusMind ToolCall 8B v2 needs about 6.8 GB of memory at Q4_K_M (a 5.2 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 12 quants, from 3.4 GB (Q2_K) to 17.0 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.6 GB.

OculusMind ToolCall 8B v2 – 8.49B‑parameter tool‑calling model

OculusMind ToolCall 8B v2 is a 8.49‑billion‑parameter Mistral‑3 model fine‑tuned for tool calls. It achieves 95.45 % correct tool choice on held‑out production turns and never loops. The model supports long context up to 262 144 tokens and runs on llama.cpp, Ollama and LM Studio.

Good at

  • Accurate tool selection
  • No tool‑call loops
  • Long‑context handling

Limits

  • No vision support
  • Requires 8 k context for memory estimates
  • Apache‑2.0 license

Best for

  • Tool‑calling assistants
  • Production‑grade agent deployment
  • Long‑context reasoning

Who it’s for. Developers building agents that need reliable tool usage and long‑context understanding. The model is suitable for laptop or desktop deployment with sufficient VRAM.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K3.4 GB 5.0 GB
Fits Get file →
Q3_K_S3.9 GB 5.5 GB
Fits Get file →
Q3_K_M4.2 GB 5.9 GB
Fits Get file →
Q3_K_L4.6 GB 6.2 GB
Fits Get file →
IQ4_XS4.7 GB 6.4 GB
Fits Get file →
Q4_K_S5.0 GB 6.6 GB
Fits Get file →
Q4_K_M5.2 GB 6.8 GB
Fits Get file →
Q5_K_S5.9 GB 7.6 GB
Tight Get file →
Q5_K_M6.1 GB 7.7 GB
Tight Get file →
Q6_K7.0 GB 8.6 GB
Too big Get file →
Q8_09.0 GB 10.7 GB
Too big Get file →
F1617.0 GB 18.6 GB
Too big Get file →

For 8 GB VRAM, use Q4_K_M (5.2 GB file, 6.8 GB memory at 8 k context). If 12 GB VRAM is available, Q5_K_M (6.06 GB file, 7.7 GB memory) offers higher quality. For the highest fidelity, Q8_0 (9.03 GB file, 10.7 GB memory) is recommended but needs more VRAM.

What GPU do you need for OculusMind ToolCall 8B v2?

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: no quant fits at an 8K context.
  • 6 GB VRAM: the best quant that fits is Q3_K_M (4.2 GB file, about 5.9 GB in use).
  • 8 GB VRAM: the best quant that fits is Q5_K_M (6.1 GB file, about 7.7 GB in use).
  • 12 GB VRAM: the best quant that fits is Q8_0 (9.0 GB file, about 10.7 GB in use).
  • 16 GB VRAM: the best quant that fits is Q8_0 (9.0 GB file, about 10.7 GB in use).
  • 24 GB VRAM: the best quant that fits is F16 (17.0 GB file, about 18.6 GB in use).

Which OculusMind ToolCall 8B v2 quant should you choose?

Q4_K_M is the usual starting point for OculusMind ToolCall 8B v2: it balances file size and quality well. Here it is a 5.2 GB file.

The Q8_0 file is 9.0 GB, about 1.7 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.

If memory is tight, the smallest file is Q2_K at 3.4 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturemistral3
Parameters8.49B
Layers34
Trained context262,144 tokens
KV cache (fp16)136 KB per token

Source

Quantized bymradermacher
Licenseapache-2.0
Downloads (HF)821
Last updated2026-10-10

Frequently asked questions about OculusMind ToolCall 8B v2

How much VRAM does OculusMind ToolCall 8B v2 need?

About 6.8 GB at Q4_K_M with an 8K context window. That is the 5.2 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 OculusMind ToolCall 8B v2 on an 8 GB GPU?

Yes, with Q5_K_M: the 6.1 GB file needs about 7.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of OculusMind ToolCall 8B v2 GGUF?

It depends on the quant: Q2_K is 3.4 GB, Q3_K_S is 3.9 GB, Q3_K_M is 4.2 GB, Q3_K_L is 4.6 GB, IQ4_XS is 4.7 GB, Q4_K_S is 5.0 GB and 6 more.

What context length does OculusMind ToolCall 8B v2 support?

The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.6 GB at 32K.

Where can I download OculusMind ToolCall 8B v2 GGUF?

The files are on Hugging Face in the mradermacher/OculusMind-ToolCall-8B-v2-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does OculusMind ToolCall 8B v2 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 this model on 8 GB VRAM?

Yes, the Q4_K_M quant uses 5.2 GB file size and requires about 6.8 GB VRAM at 8 k context.

Does this model support image input?

No, the release does not include a vision encoder; image input is not supported.

What license applies to this model?

The model is released under the Apache‑2.0 license.

Other GGUFs of OculusMind-ToolCall-8B-v2

Similar models

Browse all →

More from mradermacher

All by mradermacher →

More Oculusmind models

All Oculusmind →

Other small models

All small models →