Claus Ibsen created CAMEL-26591:
-----------------------------------
Summary: camel-jbang - AI tools: an & in an endpoint parameter,
the headers a cut answer leaves out, find with several words, and the closest
option of an EIP
Key: CAMEL-26591
URL: https://issues.apache.org/jira/browse/CAMEL-26591
Project: Camel
Issue Type: Improvement
Components: camel-jbang, camel-jbang-mcp
Reporter: Claus Ibsen
Fix For: 4.24.0
Follow-ups from the r26 run of the local-model benchmark and the reviews of
CAMEL-26568 and CAMEL-26572:
* The catalog check of a YAML route joins the parameters: of an endpoint into
the uri without encoding them. A value with an & (and no RAW), such as
filterFile: "${file:name} contains 'R&D'", is then refused with "Unknown option
'D''", although Camel runs it.
* camel_catalog_doc with includeHeaders=true is cut by the size limit: for
aws2-s3 it shows 3 of 54 headers, and CamelAwsS3Key is not among them. The note
about the cut should name the headers it left out, so that the model can ask
for one.
* camel_catalog_find does not split words: "aws2-s3 header KEY" finds nothing,
while the words one by one would.
* A filter with no match on an EIP gets no closest options; only components
have them. restConfiguration with optionsFilter=componentName now points to
rest-openapi and rest-postman, while restConfiguration's own option component
is what the model wanted.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
