davsclaus commented on PR #30345: URL: https://github.com/apache/camel/pull/30345#issuecomment-7002033509
One more option to weigh before reshaping the tool, now written up in CAMEL-27221 (the follow-up for a Markdown view of the recipes in the CLI, and for how local models choose between recipes and samples). CAMEL-23774 and this PR are now planned for 4.25.0, so there is time to get the shape right. `camel_catalog_sample` and the recipes work at different levels: a sample shows how to write one named EIP or component and where it goes, a recipe solves a problem with a whole route. Small models pick a tool by its description, and both descriptions talk about routes and snippets, so they get mixed up. Options: - **Fold the recipes into `camel_catalog_sample`**, e.g. `name=recipe:idempotent-consumer`, with the recipe ids in the list it gives without a name. One core tool fewer (so the prompt budget question of my earlier comment goes away), and small models do better with fewer tools. - **Hints in the answers**: `camel_catalog_sample name=idempotentConsumer` (also circuitBreaker, saga, throttle) ends with "recipe available: idempotent-consumer". Small models follow a hint in a tool answer much better than one in a description. - **Markdown answers**: a recipe rendered as Markdown (problem, options table, pitfalls, the route as a yaml block) is fewer tokens and easier for a small model than JSON with the YAML in an escaped string. The CLI and the terminal UI of CAMEL-27221 would use the same renderer. Folding into `camel_catalog_sample` is the direction I would go, with the hints. If you agree, this PR can keep the catalog file, the `patternRecipesJSon()` accessor and the tests, and the tool part can go into CAMEL-27221, which would make this PR smaller. Your call which way is easier for you. _Claude Code on behalf of davsclaus_ -- 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]
