AV

ava lfm25 toolcall

AvaGGUF by vitorcalviUpdated 2026-09-21
Download on Hugging Face
Parameters1.17B
Context125K
Layers16
Architecturelfm2
Smallest quant0.7 GB
Quick answer

ava lfm25 toolcall needs about 2.3 GB of memory at Q4_0 (a 0.7 GB file) with an 8K context window, so it fits on a 4 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 4.3 GB.

Ava LFM25 Toolcall – 1.17B parameter LLM for tool‑centric tasks

Ava LFM25 Toolcall is a 1.17B parameter language model built on the lfm2 architecture. It supports up to 128000 context tokens and is optimized for tool‑calling scenarios. The model is available in a Q4_0 quantized GGUF format.

Good at

  • Tool‑centric reasoning
  • Long‑context handling
  • Efficient inference

Limits

  • No license information provided
  • No vision support
  • Requires 2.3 GB VRAM at 8 k context

Best for

  • Chatbots that invoke external APIs
  • Automated workflow assistants
  • Script generation with tool calls

Who it’s for. Developers building applications that need a lightweight, tool‑aware language model. The model is suitable for projects where memory efficiency and long‑context reasoning are priorities.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q4_00.7 GB 2.3 GB
Fits Get file →

The only available quant is Q4_0, 0.7 GB file size. It needs approximately 2.3 GB VRAM at 8 k context. This is suitable for systems with at least 4 GB VRAM. No other quants are provided.

What GPU do you need for ava lfm25 toolcall?

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 Q4_0 (0.7 GB file, about 2.3 GB in use).

Which ava lfm25 toolcall quant should you choose?

Q4_0 (0.7 GB) is the middle option in this repository. The usual sweet spot between file size and quality, and the quant most people start with.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturelfm2
Parameters1.17B
Layers16
Trained context128,000 tokens
KV cache (fp16)128 KB per token

Source

Quantized byvitorcalvi
FamilyAva
Downloads (HF)12,052
Last updated2026-09-21

Frequently asked questions about ava lfm25 toolcall

How much VRAM does ava lfm25 toolcall need?

About 2.3 GB at Q4_0 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 ava lfm25 toolcall on an 8 GB GPU?

Yes, with Q4_0: the 0.7 GB file needs about 2.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of ava lfm25 toolcall GGUF?

It depends on the quant: Q4_0 is 0.7 GB.

What context length does ava lfm25 toolcall support?

The GGUF header lists a trained context length of 128,000 tokens (125K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.3 GB at 32K.

Where can I download ava lfm25 toolcall GGUF?

The files are on Hugging Face in the vitorcalvi/ava-lfm25-toolcall repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

Can I run Ava LFM25 Toolcall on 4 GB VRAM?

The Q4_0 quant requires about 2.3 GB VRAM at 8 k context, so 4 GB VRAM is sufficient.

Does the model support vision tasks?

No, the model does not include vision capabilities.

What context length can it handle?

It is trained on up to 128000 context tokens.

Similar models

Browse all →

More from vitorcalvi

All by vitorcalvi →

More Ava models

All Ava →

Other tiny models

All tiny models →