MI

Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe

MiniCPMGGUF by ewin-regUpdated 2026-07-29
Download on Hugging Face
Parameters1.08B
Context128K
Layers24
Architecturellama
Smallest quant0.7 GB
Quick answer

Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe needs about 1.4 GB of memory at Q4_K_M (a 0.7 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 6 quants, from 0.7 GB (Q4_K_M) to 2.2 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.8 GB.

MiniCPM5-1B Agentic Tooluse merged FP16 GGUF

MiniCPM5-1B Agentic Tooluse is a 1.08B parameter Llama‑style model fine‑tuned for tool‑calling. It supports XML‑style function calls and can act as a fast assistant or a chain‑of‑thought reasoner. The model is distributed as a GGUF file and does not require PEFT at inference.

Good at

  • Tool‑calling with XML style
  • Fast assistant mode
  • Chain‑of‑thought reasoning

Limits

  • No vision support
  • Requires external tool execution
  • License is other

Best for

  • Chatbots needing tool integration
  • Rapid prototyping of function‑calling agents
  • Low‑latency inference on modest GPUs

Who it’s for. Developers building agentic systems that need reliable tool‑calling. The model is suitable for projects that can parse XML‑style calls and provide external tool execution. It is ideal for teams that prefer a single GGUF file without additional adapters.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q4_K_M0.7 GB 1.4 GB
Fits Get file →
Q4_K_M0.7 GB 1.4 GB
Fits Get file →
Q8_01.2 GB 1.9 GB
Fits Get file →
Q8_01.2 GB 1.9 GB
Fits Get file →
F162.2 GB 2.9 GB
Fits Get file →
F162.2 GB 2.9 GB
Fits Get file →

For 8 GB VRAM, use the Q4_K_M quantization (file size 0.69 GB, estimated 1.4 GB memory at 8 k context). If more memory is available, Q8_0 (1.15 GB, 1.9 GB memory) offers higher precision. The F16 quantization (2.17 GB, 2.9 GB memory) requires the largest GPU memory but retains full FP16 fidelity.

What GPU do you need for Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe?

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 (2.2 GB file, about 2.9 GB in use).

Which Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe quant should you choose?

Q4_K_M is the usual starting point for Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe: it balances file size and quality well. Here it is a 0.7 GB file.

The Q8_0 file is 1.2 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.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturellama
Parameters1.08B
Layers24
Trained context131,072 tokens
KV cache (fp16)24 KB per token

Source

Quantized byewin-reg
FamilyMiniCPM
Licenseother
Downloads (HF)1,555
Last updated2026-07-29

Frequently asked questions about Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe

How much VRAM does Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe need?

About 1.4 GB at Q4_K_M with an 8K context window. That is the 0.7 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 Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe on an 8 GB GPU?

Yes, with F16: the 2.2 GB file needs about 2.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe GGUF?

It depends on the quant: Q4_K_M is 0.7 GB, Q4_K_M is 0.7 GB, Q8_0 is 1.2 GB, Q8_0 is 1.2 GB, F16 is 2.2 GB, F16 is 2.2 GB.

What context length does Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe support?

The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.8 GB at 32K.

Where can I download Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe GGUF?

The files are on Hugging Face in the ewin-reg/MiniCPM5-1B-Agentic-Tooluse-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 Minicpm5_1B_Agentic_Tooluse_Merged_Fp16_Ggufsafe use?

Hugging Face lists the license as other. 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 quantization requires about 1.4 GB VRAM at 8 k context, which fits within an 8 GB GPU.

Does the model support vision?

No, the model has no vision capabilities and only processes text.

Do I need to install any adapters for inference?

No, the GGUF file is a standalone checkpoint; no PEFT adapters are required at inference time.

Other GGUFs of MiniCPM5-1B-Agentic-Tooluse-Merged-FP16

Similar models

Browse all →

More from ewin-reg

All by ewin-reg →

More MiniCPM models

All MiniCPM →

Other tiny models

All tiny models →