Every other 4B model is chat-only โ tool calling normally needs 7โ8B. Google's "efficient" e4B breaks that rule: it uses Aperio's memory, files and web in under 3 GB of RAM. Not bulletproof, but genuinely capable for its size.
New here? The two-minute concepts primer explains parameters, tool calling and the rest โ they apply to every model, so they aren't repeated here.
The lightest tool-capable model there is. It runs comfortably where a full 8B model won't fit, which is the whole reason to choose it.
Give it room for conversation in .env:
These tasks prove the tools work โ and show you the retry habit that makes a 4B tool-user practical. When a call doesn't fire, naming the tool usually fixes it.
This is the rule-break. A 4B model storing a fact and recalling it in a brand-new conversation was impossible a generation ago.
remember and recall.Single-tool file access โ its steadiest trick once memory works.
read_file, then gives a two-sentence summary of the actual contents.read_file.Two tools in one prompt โ the practical ceiling at 4B. More than two and it starts dropping steps.
Its knowledge is frozen (~mid-2025), but unlike the chat-only 4B models it can fetch the live web.
fetch_url, returns the current answer and a source.Gemma 4 e4B is impressive engineering: real tool calling at a fraction of the usual memory cost. Choose it when you want memory and file access but can't fit a full 8B model, or want a light second model for background jobs. Just budget for the occasional retry โ at 4B, tool calling works most of the time, not every time.