github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #15670] gemma4 does not support description as a tool parameter name #56508

New Issue
Open
opened 2026-04-29 10:56:18 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-29 10:56:18 -05:00
Owner
Copy Link

Originally created by @ZoranRavic on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15670

What is the issue?

Gemma4 can see that there is a required property description, but it will not see it in the properties field.

For example if I give it a tool with those parameters:

{
    parameters: {
        type: 'object',
        properties: {
            propX: {
                type: 'string',
                description: 'Lorem ipsum 1',
            },
            description: {
                type: 'string',
                description: 'Lorem ipsum 2',
            },
            propY: {
                type: 'string',
                description: 'Lorem ipsum 3',
            },
        },
        required: ['propX', 'description', 'propY'],
    }

It will tell me that it sees the tool defined with only those properties:

{
    parameters: {
        type: 'object',
        properties: {
            propX: {
                type: 'string',
                description: 'Lorem ipsum 1',
            },
            propY: {
                type: 'string',
                description: 'Lorem ipsum 3',
            },
        },
        required: ['propX', 'description', 'propY'],
    }

Tested on v0.21.0 with gemma4:31b and gemma4:26b models. I did not check the other gemma models.

Other models that I tested can see all parameters correctly.

As a workaround I've renamed this property and after that it was able to call this tool.

Relevant log output

OS

Windows

GPU

Nvidia

CPU

AMD

Ollama version

0.21.0

Originally created by @ZoranRavic on GitHub (Apr 18, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15670 ### What is the issue? Gemma4 can see that there is a required property `description`, but it will not see it in the `properties` field. For example if I give it a tool with those parameters: ```js { parameters: { type: 'object', properties: { propX: { type: 'string', description: 'Lorem ipsum 1', }, description: { type: 'string', description: 'Lorem ipsum 2', }, propY: { type: 'string', description: 'Lorem ipsum 3', }, }, required: ['propX', 'description', 'propY'], } ``` It will tell me that it sees the tool defined with only those properties: ```js { parameters: { type: 'object', properties: { propX: { type: 'string', description: 'Lorem ipsum 1', }, propY: { type: 'string', description: 'Lorem ipsum 3', }, }, required: ['propX', 'description', 'propY'], } ``` Tested on `v0.21.0` with `gemma4:31b` and `gemma4:26b` models. I did not check the other gemma models. Other models that I tested can see all parameters correctly. As a workaround I've renamed this property and after that it was able to call this tool. ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU AMD ### Ollama version 0.21.0
GiteaMirror added the bug label 2026-04-29 10:56:18 -05:00
GiteaMirror commented 2026-04-29 10:56:20 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15670
Analyzed: 2026-04-18T18:13:36.269783

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274294599 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15670 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15670 **Analyzed**: 2026-04-18T18:13:36.269783 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#56508
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?