fix(groq): accept string values for boolean/number tool parameters#986
Open
obalaweb wants to merge 1 commit intoprism-php:mainfrom
Open
fix(groq): accept string values for boolean/number tool parameters#986obalaweb wants to merge 1 commit intoprism-php:mainfrom
obalaweb wants to merge 1 commit intoprism-php:mainfrom
Conversation
Llama models on Groq (e.g. llama-3.3-70b-versatile) serialize all tool
call arguments as JSON strings regardless of the declared schema type.
Groq validates the model output against the schema we send and rejects
any mismatch before returning it to the caller:
Groq Error [400]: tool call validation failed: parameters for tool
get_transactions did not match schema: errors: [
`/is_cash_in`: expected boolean, but got string,
`/limit`: expected number, but got string
]
Fix: wrap boolean, number, and integer property types in anyOf so that
Groq accepts either the declared type or a plain string from the model.
The caller is responsible for coercing string values to the expected
PHP type before invoking the tool handler.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #984
Llama models on Groq (e.g. llama-3.3-70b-versatile) serialize all tool call arguments as JSON strings regardless of the declared schema type. Groq validates the model output against the schema we send and rejects any mismatch before returning it to the caller:
Groq Error [400]: tool call validation failed: parameters for tool
get_transactions did not match schema: errors: [
/is_cash_in: expected boolean, but got string,/limit: expected number, but got string]
Fix: wrap boolean, number, and integer property types in anyOf so that Groq accepts either the declared type or a plain string from the model. The caller is responsible for coercing string values to the expected PHP type before invoking the tool handler.