llmrun
beamcoreGemma3ForCausalLM

Tools — Hardware Requirements & GPU Compatibility

ChatFunctions

Tools is a 268M-parameter open language model from beamcore. It supports a context window of up to 32,768 tokens. At Q4_K_M it needs about 0.48 GB of VRAM — see which GPUs and Macs can run it below.

268M params · dense33K contextGemma Terms34 downloads2 likes
S

Runs great on a 24 GB GPU

Runs from8 GB Q4_K_M · 32KBest on24 GB Q4_K_M · ~1365 tok/s · 32KMacs from8 GB Q4_K_M · ~149 tok/s

Gemma Terms

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Tools

One recommended way. Every other method, OS and quant is in the step-by-step guide.Each way opens a step-by-step guide for your OS and quant.

Recommended

vLLM
one command · needs vLLM installed
$vllm serve beamcore/tools --max-model-len 16384

vLLM repo with its own quantisation

Download: Weights on Hugging Face

install, OS, other quants

Ways to runOther ways

each opens step-by-step

Run in cloud

Runs on RTX 3060 12GB (11 GB headroom) · Q4_K_M

Generation speed
~488 tok/s
generation speed
Cost per 1M output tokens
$0.034
per 1M output tokens

How Much VRAM Does Tools Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KOn RTX 4090 (reference)
0.4 GB0.5 GB2-bit · K-quant — 2-bit quantization with K-quant improvementsFits: 32K context · ~1489 tok/s
0.5 GB0.5 GB3-bit medium — 3-bit medium quantizationFits: 32K context · ~1456 tok/s
0.5 GB0.6 GB4-bit medium — 4-bit medium quantization — most popular sweet spotFits: 32K context · ~1365 tok/s
0.5 GB0.6 GB5-bit medium — 5-bit medium quantization — good quality/size tradeoffFits: 32K context · ~1285 tok/s
0.5 GB0.6 GB6-bit, very good — 6-bit quantization, very good qualityFits: 32K context · ~1213 tok/s
0.6 GB0.7 GB8-bit, near-lossless — 8-bit quantization, near-losslessFits: 32K context · ~1111 tok/s
0.9 GB0.9 GB16-bit · bfloat — Brain floating point 16 — preferred for trainingFits: 32K context · ~762 tok/s
est.calculated, no published file yet

Selected Q4_K_M

4-bit medium quantization

0.5GBat 16K context

Weights
0.2 GB
KV cache
0.1 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 23.5 GB free · ~1365 tok/s

≥50 tok/s needs ≥37 GB/s · RTX 5090 ~2427, RTX 3090 Ti ~1365

Which Hardware Can Run Tools?

Q4_K_M · 0.5 GB

Tools (Q4_K_M) requires 0.5 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 1+ GB is recommended. Using the full 33K context window can add up to 0.1 GB, bringing total usage to 0.6 GB. 52 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 163 devices with unified memory can run Tools, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M
8 GB · RTX 4060Q4_K_M · 0.5 GB · ~368 tok/s · 32K8 GB tier →
12 GB · RTX 3060 12GBQ4_K_M · 0.5 GB · ~488 tok/s · 32K12 GB tier →
16 GB · RTX 5060 Ti 16GBQ4_K_M · 0.5 GB · ~607 tok/s · 32K16 GB tier →
24 GB · RTX 4090referenceQ4_K_M · 0.5 GB · ~1365 tok/s · 32K24 GB tier →
Mac 32 GB · Mac Mini M4Q4_K_M · 0.5 GB · ~175 tok/s · 32KMacs →
Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 0.5 GB · ~796 tok/s · 32KMacs →

Alternatives to Tools

Similar models

2
ModelScoreVRAMtok/sWhy it is similar
Gemma 3 270M ITGoogle—1.2 GB~3640same size
Functiongemma 270M ITGoogle—1.6 GB~1111same size

Specifications

Publisher
beamcore
Parameters
268M
Architecture
Gemma3ForCausalLM
Context Length
32,768 tokens
Vocabulary Size
262,144
Release Date
2026-06-08
License
Gemma Terms

Frequently Asked Questions

How much VRAM does Tools need?

Tools requires 0.5 GB of VRAM at Q4_K_M, or 0.9 GB at BF16.

VRAM = Weights + KV Cache + Overhead

Weights = 268M × 4.8 bits ÷ 8 = 0.2 GB

KV Cache + Overhead ≈ 0.3 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 0.4 GB (at full 33K context)

VRAM usage by quantization

0.5 GB
0.6 GB

Learn more about VRAM estimation →

What's the best quantization for Tools?

For Tools, Q4_K_M (0.5 GB) offers the best balance of quality and VRAM usage. Q5_K_M (0.5 GB) provides better quality if you have the VRAM. The smallest option is Q2_K at 0.4 GB.

VRAM requirement by quantization

Q2_K
0.4 GB
Q4_K_M ★
0.5 GB
Q5_K_M
0.5 GB
Q6_K
0.5 GB
Q8_0
0.6 GB
BF16
0.9 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run Tools on a Mac?

Yes — MacBook Air 13" M3 (8 GB) and 145 other Macs can run Tools. Apple Silicon uses unified memory, so the model shares RAM with the system. At Q4_K_M you need at least 0.5 GB of usable unified memory (RAM minus macOS overhead).

Can I run Tools locally?

Yes — Tools can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Tools?

At Q4_K_M, Tools can reach ~10000 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~1365 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: NVIDIA B200 → 8000 ÷ 0.48 × 0.65 = ~10833 tok/s

Estimated speed at Q4_K_M (0.5 GB)

~10833 tok/s
~1365 tok/s
~10833 tok/s
~10000 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of Tools?

At Q4_K_M, the download is about 0.16 GB. The full-precision BF16 version is 0.54 GB. The smallest option (Q2_K) is 0.11 GB.

Which GPUs can run Tools?

52 consumer GPUs can run Tools at Q4_K_M. Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 52 GPUs have plenty of headroom for comfortable inference.

Which devices can run Tools?

163 devices with unified memory can run Tools at Q4_K_M (0.5 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.