davsclaus opened a new pull request, #30607:
URL: https://github.com/apache/camel/pull/30607

   [CAMEL-27314](https://issues.apache.org/jira/browse/CAMEL-27314)
   
   The tool loop of camel-openai runs two kinds of tools: MCP server tools 
(`mcpServer.*`) and route tools (`tags`, routes that start with `ai-tool:`). 
`McpToolCallExecutor` runs both, and the endpoint merges route tools into the 
same tool state, so the streaming fallback applies to them too. The option 
descriptions and docs said MCP only, so a model reading them through the 
catalog or the Camel MCP server could add an MCP server it does not need.
   
   Changes (wording only, no behaviour change):
   - `autoToolExecution`: says it runs both MCP and route tools, and what 
`false` returns.
   - `maxAgenticTokens`: "tool loop" instead of "MCP agentic loop".
   - `tags`: route tools run in the same loop and need no MCP server.
   - The chat-completion body type text, the streaming INFO log line, and the 
javadoc of the loop events and trace no longer say MCP only.
   - `openai-component.adoc` streaming note and the `openai-mcp.adoc` intro, 
loop steps and error table now cover route tools.
   - New `=== Route Tools` section in `openai-mcp.adoc`: `tags` on the endpoint 
plus one `ai-tool` route, in Java, XML and YAML tabs (the YAML and XML were 
checked with `camel_validate_source`). It links to the ai-tool component docs.
   
   The catalog JSON and doc copies and `OpenAIEndpointBuilderFactory` were 
regenerated. Built with `mvn -o formatter:format impsort:sort package -pl 
components/camel-ai/camel-openai`.
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to