JiriOndrusek opened a new issue, #9534:
URL: https://github.com/apache/camel-quarkus/issues/9534

   ### Problem
   A review of the `ai-tool` extension documentation (Camel Quarkus 3.40.1) 
against the code found inaccuracies and gaps.
   
   ### Inaccuracies
   - `usage.adoc`, first line: it names `camel-quarkus-langchain4j-tools` as a 
consumer of the tool registry. `camel-langchain4j-tools` never reads 
`AiToolRegistry` and is deprecated since Camel 4.22 (use `camel-ai-tool` with 
`langchain4j-agent`). The real consumers are `camel-quarkus-langchain4j-agent`, 
`camel-quarkus-openai` and `camel-quarkus-mcp-server`.
   - The example in the "Tag-based grouping" section carries the comment 
"Untagged tool - available to all producers". The section "Who receives 
registered tools" on the same page says that a Camel agent 
(`langchain4j-agent`) without `tags` receives no registry tools. The page 
contradicts itself; a precise wording would be "available to every tag query 
(and to `@RegisterAiService` without `@CamelAiTools`)".
   
   ### Missing in `usage.adoc`
   - The `argSchema` option, the tool annotation hints, `title` and 
`returnDirect` are not mentioned (the page only links to the Camel docs).
   - The `camel-quarkus-ai-tool` dependency is required for the LangChain4j 
bridge (only in the 3.40.0 migration guide).
   - `@CamelAiTools`: a blank value is a build error, only a single tag is 
supported (no comma list), and Camel agent services are excluded from the 
bridge.
   - Behaviour that surprises users: argument names starting with `camel` are 
silently dropped, duplicate tool names under the same tag throw, undeclared 
arguments are dropped with a warning.
   
   _Generated with [Claude Code](https://claude.com/claude-code) on behalf of 
@JiriOndrusek_


-- 
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