Model reference · open weights

LFM2-Tool

LLMs LiquidAI Text gen 1 build Its own licence terms 1k dl/mo

LFM2-Tool is an open-weight language model from LiquidAI. LFM2-1.2B-Tool (BF16) weighs 2.3 GB; the smallest configuration that runs it is RTX 3060 12 GB.

For self-hosting, compare this build's requirements below with the GPU you plan to rent.

  • LFM2-Tool is a 1.2B parameter text-generation model by LiquidAI designed for concise and precise tool calling on mobile and edge devices.
  • It supports a 128,000 token context length and operates in English, Arabic, Chinese, French, German, Japanese, Korean, Portuguese, and Spanish.
  • The model uses a non-thinking approach to execute function calls and is available under an other licence.

Summary of the LiquidAI/LFM2-1.2B-Tool model card, 2026-10-01

What it is

Released byLiquidAI
Released2025-09-03
Parameters1.2B
VRAM2.3 GB for the weights

What it runs on

Memory and cards for LFM2-1.2B-Tool (BF16)

2.3 GBweights, file size
631 MBruntime overhead, at least
128,000 tokenscontext max

How much memory each request adds isn't estimated yet for this architecture. The weights need at least the cards below, plus room for the context.

CardWeights alone
RTX 3060 12 GBfits
RTX 4060 Ti 16 GBfits
RTX 3090 24 GBfits
RTX 4090 24 GBfits
RTX 5090 32 GBfits
L40S 48 GBfits
A100 80 GBfits
H100 80 GBfits
RTX PRO 6000 Blackwell 96 GBfits
DGX Spark (GB10) 128 GB unifiedfits
H200 141 GBfits
B200 180 GBfits

From the model card

What LiquidAI says about LFM2-Tool

Read the model card

src="https://cdn-uploads.huggingface.co/production/uploads/61b8e2ba285851687028d395/2b08LKpev0DNEk6DlnWkY.png" alt="Liquid AI" style="width: 100%; max-width: 100%; height: auto; display: inline-block; margin-bottom: 0.5em; margin-top: 0.5em;" />

LFM2-1.2B-Tool

Based on LFM2-1.2B, LFM2-1.2B-Tool is designed for concise and precise tool calling. The key challenge was designing a non-thinking model that outperforms similarly sized thinking models for tool use.

Use cases:

  • Mobile and edge devices requiring instant API calls, database queries, or system integrations without cloud dependency.
  • Real-time assistants in cars, IoT devices, or customer support, where response latency is critical.
  • Resource-constrained environments like embedded systems or battery-powered devices needing efficient tool execution.

You can find more information about other task-specific models in this blog post.

📄 Model details

Generation parameters: We recommend using greedy decoding with a temperature=0.

System prompt: The system prompt must provide all the available tools

Supported languages: English, Arabic, Chinese, French, German, Japanese, Korean, Portuguese, and Spanish.

Tool use: It consists of four main steps:

  1. Function definition: LFM2 takes JSON function definitions as input (JSON objects between and special tokens), usually in the system prompt
  2. Function call: LFM2 writes Pythonic function calls (a Python list between and special tokens), as the assistant answer.
  3. Function execution: The function call is executed and the result is returned (string between and special tokens), as a "tool" role.
  4. Final answer: LFM2 interprets the outcome of the function call to address the original user prompt in plain text.

Here is a simple example of a conversation using tool use:

List of tools: [{"name": "get_candidate_status", "description": "Retrieves the current status of a candidate in the recruitment process", "parameters": {"type": "object", "properties": {"candidate_id": {"type": "string", "description": "Unique identifier for the candidate"}}, "required": ["candidate_id"]}}]
What is the current status of candidate ID 12345?
The candidate with ID 12345 is currently in the "Interview Scheduled" stage for the position of Clinical Research Associate, with an interview date set for 2023-11-20.

[!WARNING] ⚠️ The model supports both single-turn and multi-turn conversations.

📈 Performance

For edge inference, latency is a crucial factor in delivering a seamless and satisfactory user experience. Consequently, while test-time-compute inherently provides more accuracy, it ultimately compromises the user experience due to increased waiting times for function calls.

Therefore, the goal was to develop a tool calling model that is competitive with thinking models, yet operates without any internal chain-of-thought process.

We evaluated each model on a proprietary benchmark that was specifically designed to prevent data contamination. The benchmark ensures that performance metrics reflect genuine tool-calling capabilities rather than memorized patterns from training data.

🏃 How to run

You can use the following Colab notebooks for easy inference and fine-tuning:

NotebookDescriptionLink
InferenceRun the model with Hugging Face's transformers library.
SFT (TRL)Supervised Fine-Tuning (SFT) notebook with a LoRA adapter using TRL.
DPO (TRL)Preference alignment with Direct Preference Optimization (DPO) using TRL.
SFT (Axolotl)Supervised Fine-Tuning (SFT) notebook with a LoRA adapter using Axolotl.
SFT (Unsloth)Supervised Fine-Tuning (SFT) notebook with a LoRA adapter using Unsloth.

📬 Contact

  • If you are interested in custom solutions with edge deployment, please contact our sales team.

Citation

@article{liquidai2025lfm2,
 title={LFM2 Technical Report},
 author={Liquid AI},
 journal={arXiv preprint arXiv:2511.23404},
 year={2025}
}

Quoted from the model card on Hugging Face. The full card is behind the Hugging Face link above.

© 2026 AxForge · EU-hosted AI infrastructure Pricing Docs Trust Privacy Terms