OC

OculusMind ToolCall 8B v2

OculusmindGGUF by mradermacherUpdated 2026-10-10
Download on Hugging Face
Parameters8.49B
Context256K
Layers34
Architecturemistral3
Smallest quant0.0 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 25 quants, from 0.0 GB to 7.0 GB (Q6_K). 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 an 8.49‑billion‑parameter Mistral‑3 model fine‑tuned for tool‑calling. It achieves 95.45 % agreement with production tool choices and zero loop rate on held‑out evals. The model supports long context up to 262,144 tokens and is released under Apache‑2.0.

Good at

  • Tool‑calling with high accuracy
  • Zero degenerate loops
  • Long‑context handling up to 262,144 tokens

Limits

  • No vision support – text only
  • Requires at least 8 GB VRAM for Q8_0 build
  • Large context increases memory usage

Best for

  • Deploying lightweight agents on laptops
  • Building custom tool‑calling assistants
  • Running on llama.cpp or Ollama

Who it’s for. Developers building agent‑based applications that need reliable tool calls. The model is suitable for users who require high tool‑choice accuracy and long‑context reasoning without vision input.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
—0.0 GB 1.6 GB
Fits Get file →
IQ1_S2.1 GB 3.8 GB
Fits Get file →
IQ1_M2.3 GB 3.9 GB
Fits Get file →
IQ2_XXS2.5 GB 4.2 GB
Fits Get file →
IQ2_XS2.7 GB 4.4 GB
Fits Get file →
IQ2_S2.9 GB 4.5 GB
Fits Get file →
IQ2_M3.1 GB 4.7 GB
Fits Get file →
Q2_K_S3.1 GB 4.8 GB
Fits Get file →
Q2_K3.4 GB 5.0 GB
Fits Get file →
IQ3_XXS3.5 GB 5.1 GB
Fits Get file →
IQ3_XS3.7 GB 5.4 GB
Fits Get file →
Q3_K_S3.9 GB 5.5 GB
Fits Get file →
IQ3_S3.9 GB 5.5 GB
Fits Get file →
IQ3_M4.0 GB 5.6 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.3 GB
Fits Get file →
Q4_04.9 GB 6.6 GB
Fits Get file →
IQ4_NL4.9 GB 6.6 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 →
Q4_15.4 GB 7.1 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 →

For 8 GB VRAM use Q8_0 (9.0 GB). With 12 GB VRAM, Q4_0 (4.94 GB) or Q4_K_M (5.2 GB) provide a good balance of size and memory. For 16 GB VRAM, Q5_K_M (6.06 GB) offers higher quality while staying within limits.

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: the best quant that fits is IQ1_M (2.3 GB file, about 3.9 GB in use).
  • 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 Q6_K (7.0 GB file, about 8.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.

If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.

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)2,463
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: file is 0.0 GB, IQ1_S is 2.1 GB, IQ1_M is 2.3 GB, IQ2_XXS is 2.5 GB, IQ2_XS is 2.7 GB, IQ2_S is 2.9 GB and 19 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-i1-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 Q8_0 GGUF build is 9.0 GB and can run on 8 GB VRAM with some performance trade‑offs.

Does the model support image input?

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

What license does the model use?

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 →