Model Page: FunctionGemma
Resources and Technical Documentation:
Terms of Use: Terms
Authors: Google DeepMind
Summary description and brief definition of inputs and outputs.
NOTE
FunctionGemma is intended to be fine-tuned for your specific function-calling task, including multi-turn use cases.
FunctionGemma is a lightweight, open model from Google, built as a foundation for creating your own specialized function calling models. FunctionGemma is not intended for use as a direct dialogue model, and is designed to be highly performant after further fine-tuning, as is typical of models this size. Built on the Gemma 3 270M model and with the same research and technology used to create the Gemini models, FunctionGemma has been trained specifically for function calling. The model has the same architecture as Gemma 3, but uses a different chat format. The model is well suited for text-only function calling. The uniquely small size makes it possible to deploy in environments with limited resources such as laptops, desktops or your own cloud infrastructure, democratizing access to state of the art AI models and helping foster innovation for everyone. Furthermore, akin to the base Gemma 270M, the model has been optimized to be extremely versatile, performant on a variety of hardware in single turn scenarios, but should be finetuned on single turn or multiturn task specific data to achieve best accuracy in specific domains. To demonstrate how specializing the 270M parameter model can achieve high performance on specific agentic workflows, we have highlighted two use cases in the Google AI Edge Gallery app.
Tiny Garden: A model fine-tuned to power a voice-controlled interactive game. It handles game logic to manage a virtual plot of land, decomposing commands like "Plant sunflowers in the top row" and "Water the flowers in plots 1 and 2" into app-specific functions (e.g., plant_seed, water_plots) and coordinate targets. This demonstrates the model's capacity to drive custom app mechanics without server connectivity.
Mobile Actions: To empower developers to build their own expert agents, we have published a dataset and fine-tuning recipe to demonstrate fine-tuning FunctionGemma. It translates user inputs (e.g., "Create a calendar event for lunch," "Turn on the flashlight") into function calls that trigger Android OS system tools. This interactive notebook demonstrates how to take the base FunctionGemma model and build a "Mobile Actions" fine tune from scratch for use in the Google AI Edge gallery app. This use case demonstrates the model's ability to act as an offline, private agent for personal device tasks.
The following is a code example of how to use FunctionGemma to generate a function call from a JSON definition using the Hugging Face Transformers library.
First install the dependencies:
$ pip install torch $ pip install transformers
Then load the model and the processor using Transformers:
from transformers import AutoProcessor, AutoModelForCausalLM
processor = AutoProcessor.from_pretrained("google/functiongemma-270m-it", device_map="auto")
model = AutoModelForCausalLM.from_pretrained("google/functiongemma-270m-it", dtype="auto", device_map="auto")
Define the function definition using JSON schema, then set a system instruction using the developer role. This is required to let the model know it should use the function(s) provided. Add a user query as input to the model and then generate the output. The model will then generate one or more function calls that it wants the developer to make on its behalf.
weather_function_schema = {
"type": "function",
"function": {
"name": "get_current_temperature",
"description": "Gets the current temperature for a given location.",
"parameters": {
"type": "object",
"properties": {
"location": {
"type": "string",
"description": "The city name, e.g. San Francisco",
},
},
"required": ["location"],
},
}
}
message = [
# ESSENTIAL SYSTEM PROMPT:
# This line activates the model's function calling logic.
{
"role": "developer",
"content": "You are a model that can do function calling with the following functions"
},
{
"role": "user",
"content": "What's the temperature in London?"
}
]
inputs = processor.apply_chat_template(message, tools=[weather_function_schema], add_generation_prompt=True, return_dict=True, return_tensors="pt")
out = model.generate(**inputs.to(model.device), pad_token_id=processor.eos_token_id, max_new_tokens=128)
output = processor.decode(out[0][len(inputs["input_ids"][0]):], skip_special_tokens=True)
print(output)
# <start_function_call>call:get_current_temperature{location:<escape>London<escape>}<end_function_call>
For more detailed examples see the Gemma documentation.
Data used for model training and how the data was processed.
These models were trained on a dataset of text data that includes a wide variety of sources. The model was trained with 6T tokens. The knowledge cutoff date for the training data was August 2024. There are the key components:
Here are the key data cleaning and filtering methods applied to the training data:
Details about the model internals.
Gemma was trained using Tensor Processing Unit (TPU) hardware (TPUv4p, TPUv5p and TPUv5e). Training vision-language models (VLMs) requires significant computational power. TPUs, designed specifically for matrix operations common in machine learning, offer several advantages in this domain:
Training was done using JAX and
ML Pathways.
JAX allows researchers to take advantage of the latest generation of hardware,
including TPUs, for faster and more efficient training of large models. ML
Pathways is Google's latest effort to build artificially intelligent systems
capable of generalizing across multiple tasks. This is specially suitable for
foundation models, including large language models like these ones.
Together, JAX and ML Pathways are used as described in the paper about the
Gemini family of models; "the 'single
controller' programming model of Jax and Pathways allows a single Python process
to orchestrate the entire training run, dramatically simplifying the development
workflow."
Model evaluation metrics and results.
| Benchmark | n-shot | Function Gemma 270m |
|---|---|---|
| BFCL Simple | 0-shot | 61.6 |
| BFCL Parallel | 0-shot | 63.5 |
| BFCL Multiple | 0-shot | 39 |
| BFCL Parallel Multiple | 0-shot | 29.5 |
| BFCL Live Simple | 0-shot | 36.2 |
| BFCL Live Parallel | 0-shot | 25.7 |
| BFCL Live Multiple | 0-shot | 22.9 |
| BFCL Live Parallel Multiple | 0-shot | 20.8 |
| BFCL Relevance | 0-shot | 61.1 |
| BFCL Irrelevance | 0-shot | 70.6 |
Impact on Performance after Fine-tuning on Mobile Actions Dataset
To demonstrate the value of specialization for small language models, we
compared the base FunctionGemma model against the fine-tuned model using the
"Mobile Actions"
recipe.
Fine-tuning significantly improved the base FunctionGemma model's ability to
correctly identify and format mobile system calls.
Model | Eval results for Mobile Actions |
|---|---|
Base FunctionGemma model | 58% |
Mobile Actions Fine-Tune | 85% |
On-Device Performance of the Gemma 270m Fine-tuned Use Cases
We evaluated the fine-tuned use cases on a Samsung S25 Ultra to assess on-device
latency and memory footprint.
Mobile Actions On Device Performance
Backend | Quantization scheme | Context length | Prefill (tokens per second) | Decode (tokens per second) | Time-to-first-token (seconds) | Model Size (MB) | Peak RSS Memory (MB) |
|---|---|---|---|---|---|---|---|
CPU | dynamic_int8 | 1024 | 1718 | 125.9 | 0.3 | 288 | 551 |
Tiny Garden On Device Performance
Backend | Quantization scheme | Context length | Prefill (tokens per second) | Decode (tokens per second) | Time-to-first-token (seconds) | Model Size (MB) | Peak RSS Memory (MB) |
|---|---|---|---|---|---|---|---|
CPU | dynamic_int8 | 1024 | 1743 | 125.7 | 0.3 | 288 | 549 |
Ethics and safety evaluation approach and results.
Our evaluation methods include structured evaluations and internal red-teaming testing of relevant content policies. Red-teaming was conducted by a number of different teams, each with different goals and human evaluation metrics. These models were evaluated against a number of different categories relevant to ethics and safety, including:
For all areas of safety testing, we saw major improvements in the categories of child safety, content safety, and representational harms relative to previous Gemma models. All testing was conducted without safety filters to evaluate the model capabilities and behaviors. The model produced minimal policy violations, and showed significant improvements over previous Gemma models' performance with respect to ungrounded inferences. A limitation of our evaluations was they included only English language prompts.
These models have certain limitations that users should be aware of.
This model is not intended for use as a direct dialogue model.
Open Large Language Models (LLMs) have a wide range of applications across
various industries and domains. The following list of potential uses is not
comprehensive. The purpose of this list is to provide contextual information
about the possible use-cases that the model creators considered as part of model
training and development.
The development of large language models (LLMs) raises several ethical concerns. In creating an open model, we have carefully considered the following:
Risks identified and mitigations:
At the time of release, this family of models provides high-performance open large language model implementations designed from the ground up for Responsible AI development compared to similarly sized models.