You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Federico Mariani (Jira)" <ji...@apache.org> on 2026/05/27 09:13:00 UTC
[jira] [Updated] (CAMEL-23621) camel-langchain4j-tools / camel-langchain4j-agent / camel-spring-ai-tools: tool argument headers should be filtered against declared parameters
[ https://issues.apache.org/jira/browse/CAMEL-23621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Federico Mariani updated CAMEL-23621:
-------------------------------------
Fix Version/s: 4.18.3
4.21.0
> camel-langchain4j-tools / camel-langchain4j-agent / camel-spring-ai-tools: tool argument headers should be filtered against declared parameters
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-23621
> URL: https://issues.apache.org/jira/browse/CAMEL-23621
> Project: Camel
> Issue Type: Improvement
> Components: camel-langchain4j-agent, camel-langchain4j-tools, camel-spring-ai
> Affects Versions: 4.20.0
> Reporter: Federico Mariani
> Assignee: Federico Mariani
> Priority: Major
> Fix For: 4.18.3, 4.21.0
>
>
> hen LLM tool calls are processed, all JSON field names from the tool call arguments are set as Exchange headers without filtering against the tool's declared parameter schema.
> For example, a tool declared with parameter.userId=string will accept any field name from the LLM response as a header, not just userId. Only declared parameters should flow into the Exchange.
>
> The fix should filter incoming field names against the tool specification's declared parameters and skip any undeclared ones.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)