Claus Ibsen created CAMEL-26572:
-----------------------------------
Summary: camel-jbang - AI tools: catalog lookups find message
headers and file: functions, and a filter with no match says where the option is
Key: CAMEL-26572
URL: https://issues.apache.org/jira/browse/CAMEL-26572
Project: Camel
Issue Type: Improvement
Components: camel-jbang, camel-jbang-mcp
Reporter: Claus Ibsen
Fix For: 4.24.0
In the r26 run of the local-model benchmark (qwen3.6, 7 rounds), 12 failed
steps of the new example set ended with no accepted write. Each used all 25
calls and sent one catalog lookup 6 to 23 times with the same arguments (r25: 3
such steps). Most of them looked for something the lookup cannot find. In r26,
19 filters matched nothing (r25: 4).
* camel_catalog_doc optionsFilter searches the option names, descriptions and
groups, not the message headers: aws2-s3 with optionsFilter=CamelAwsS3Key was
sent 17 times. camel_catalog_find does not find header names either ("Nothing
in the catalog matches", 16 finds in one run).
* The file: functions are in the catalog entry of the file language, not in
simple: simple with optionsFilter=file:name.noext matched nothing (14 calls).
* apiContextPath was looked for on the rest component (23 calls in one run). It
is an option of restConfiguration, and nothing says so. statusCode and status
matched no option either.
Proposal, with no change to tool names or arguments:
* optionsFilter of a component also searches its message headers, and returns
the headers that match.
* camel_catalog_find finds header names.
* The optionsFilter of simple also searches the file: functions.
* A filter with no match says which EIP, component or configuration has an
option of that name, such as "apiContextPath is an option of restConfiguration".
Related: CAMEL-25639 (consolidation of the tool surface).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
