[
https://issues.apache.org/jira/browse/CAMEL-24828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-24828.
---------------------------------
Fix Version/s: 4.23.0
Resolution: Fixed
Merged in https://github.com/apache/camel/pull/26607 (commit 0be59c361c05) for
4.23.0.
> camel-jbang-mcp: examples tools should follow the example groups and accept
> optional arguments
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-24828
> URL: https://issues.apache.org/jira/browse/CAMEL-24828
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.23.0
>
>
> The MCP tools camel_catalog_examples / camel_catalog_example_file in
> camel-jbang-mcp (and the matching list_examples / get_example_file in the
> camel-jbang-core AI tool registry) lag behind the reorganized examples
> catalog (CAMEL-24824):
> * In camel-jbang-mcp the three arguments (filter, level, limit) are not
> declared with required = false, so a call without all of them fails with
> "Missing required argument: ...". The other tools in the module declare
> optional arguments correctly.
> * The tool descriptions still say level is a difficulty (beginner,
> intermediate, advanced). The catalog now uses the 11 group levels
> (quick-start, run, transform, route, fail-well, connect, connect-service,
> contracts, ai, cloud, showcase), so the model filters with values that match
> nothing.
> * The new metadata (order, teaches, infraServices) is not returned and there
> is no way to list the groups with their title and intro, so an AI agent
> cannot present the ladder the same way camel run --example does.
> * The core registry variant caps the result at 20 entries with no limit
> argument, so an unfiltered listing silently drops half of the 40 examples.
> Proposed:
> * make filter, level and limit optional (limit default 50)
> * return order, teaches, infraServices and bundled, sorted by group order
> then rung order
> * add a group listing (group headers with title, intro and example names) so
> the agent can browse by group
> * update the descriptions to talk about groups
> * apply the same to the core AI tool registry so both stay in sync
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
